Process applicability condition not working - table of items

ddumas

I have a table of items, which I need to display a new SendSingleEmail process icon that the user can click on to run a process that takes as input the current row.

For the table of items, I have an applicability condition set to:

ProjectVendor.SC_ApprovalStatus='Approved' AND ProjectVendor.SC_ProjectOwnerLogin=LoggedInEmployee.LoginName

The SC_xxx attributes are shortcuts.

The icon does not show up to the user for a [true] condition (bad).

As a debug I created another DEBUG_process with no applicability condition to just display the above values. It displays fine (shows all correct values to a true condition), so not sure why the icon does not display on the SendSingleEmail process.

aware_support

Check Tomcat output - it should display the results of applicability conditions evaluation and the values used

ddumas

aware_support wrote
Check Tomcat output - it should display the results of applicability conditions evaluation and the values used

Got that - Tomcat log:

Condition evaluated to false:Approved=Approved AND =jman

So, as you can see from above, the ProjectVendor.SC_ProjectOwnerLogin, (defined as Project.Owner.LoginName) is evaluating to null. However, in the debig process that doea a DISPLAY MESSAGE, ProjectVendor.SC_ProjectOwnerLogin displays with the correct value.

So, I am not sure why the applicability condition is evaluating that same code to null.

aware_support

Do you display this value in the table? Does it display OK? Maybe it is protected by an access level or protection rule?

ddumas

aware_support wrote
Do you display this value in the table? Does it display OK? Maybe it is protected by an access level or protection rule?

The processes have full access by the Employee access level. An Employee logs in and runs the process.

Regardless, I display the same values in a DISPLAY MESSAGE, in another operation for the same table of items (with no applicability defined), so if it's not null in the message display, I do not see how it is null when evaluated in the applicability for another operation based on a process that takes the same input object.