This is an old revision of the document!
Table of Contents
Workflow Conditions
TBD 
: Explain how the different conditions work.
Hidden and Hard to find Features
Comparing Last Modified By User and the current Assigned User
When defining the conditions we have access to all the fields of the main module of the workflow and all it's related entities on the left hand side of the condition, but on the right hand side we can only access the fields directly related to the main module, not the fields of the related entities.
In fact, the use cases for this type of conditions is very limited. In all the years that we have been working with coreBOS this has rarely come up and we usually solve it with some additional code for the specific case.
Based on this question from a forum member:
To solve this use case, which is common, we have enhanced coreBOS (starting at commit or version 5.6) to support accessing the fields of the “assigned to” user of the main module.
It is ONLY for the fields of the “assigned user” because those are already present when evaluating the condition, no extra effort is needed except picking them up.
The syntax is a little different to make the code easier, maybe we will enhance that some day to work as the left hand side of the condition. Currently the syntax has to be:
assigned_user_id : (Users) {field name}
where {field name} has to be the internal field name of the user module. For example to access the user name we would use user_name and to access the first name we would use first_name.
Once applied the code change detailed here, we can answer the question above as seen in the next image:
