accessibility condition set on operation fails

ddumas

I have a condition on a form table of items (set for the item operation), set as follows. The first statement succeeds (If Approved, and operation displays). However, the second one (after the AND) is not working. It is always false, so the operation is always hidden. The SC_ attributes are shortcuts.

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

To test I created another operation to display the values of ProjectVendor.SC_ProjectOwnerLogin and LoggedInSystemUser.LoginName I do a REPORT ERROR, and the values are identical, so the second condition should return true. So, not sure why it always evaluates to false.

ddumas

As an additional test, I created a test process, called from a new operation in the same table of items that does the following:

IF ProjectVendor.SC_ProjectOwnerLogin=LoggedInSystemUser.LoginName THEN
REPORT ERROR 'equal' + ProjectVendor.SC_ProjectOwnerLogin + '= ' + LoggedInSystemUser.LoginName
else
REPORT ERROR 'not equal: ' + ProjectVendor.SC_ProjectOwnerLogin + '<> ' + LoggedInSystemUser.LoginName

This succeeds (else does not get executed, and equal code executes). So, there seems to be a difference (problem) in the applicability evaluation vs the test process code above. They should both evaluate the same.

RocketRod

Try it by replacing the shortcuts with the actual values.

ddumas

RocketRod wrote
Try it by replacing the shortcuts with the actual values.

applicability conditions do not allow references, so you have to use shortcuts to get around that limitation.

It seems like a bug of some sort, because when used in a process, the statement works.

customaware

I have the same problem.

In the Applicability I have tried...

LeaveApplicationRejection.EmployeeSC=LoggedInRegularUser.DisplayName

Does not work.

tried....

LeaveApplicationRejection.LeaveApplication.EmployeeNameSC=LoggedInRegularUser.DisplayName

Does not work

tried....

LeaveApplicationRejection.LeaveApplication.Employee.DisplayName=LoggedInRegularUser.DisplayName

Does not work...Reference Error.

Certainly looks like a bug to me

However...finally found a workaround (but would like the bug fixed.)

In my BO LeaveApplicationRejections I created a text Attribute called EmployeeDisplayName and set it with a rule on the BO

LeaveApplicationRejection.EmployeeDisplayName=LeaveApplicationRejection.LeaveApplication.Employee.DisplayName

then in the Applicability....this works.

LeaveApplicationRejection.EmployeeDisplayName=LoggedInRegularUser.DisplayName

Go Figure!

ddumas

eagles9999 wrote
I have the same problem.

In the Applicability I have tried...

LeaveApplicationRejection.EmployeeSC=LoggedInRegularUser.DisplayName

Does not work.

tried....

LeaveApplicationRejection.LeaveApplication.EmployeeNameSC=LoggedInRegularUser.DisplayName

Does not work

tried....

LeaveApplicationRejection.LeaveApplication.Employee.DisplayName=LoggedInRegularUser.DisplayName

Does not work...Reference Error.

Certainly looks like a bug to me

However...finally found a workaround (but would like the bug fixed.)

In my BO LeaveApplicationRejections I created a text Attribute called EmployeeDisplayName and set it with a rule on the BO

LeaveApplicationRejection.EmployeeDisplayName=LeaveApplicationRejection.LeaveApplication.Employee.DisplayName

then in the Applicability....this works.

LeaveApplicationRejection.EmployeeDisplayName=LoggedInRegularUser.DisplayName

Go Figure!

Right 🙂 I started creating actual attributes in my objects, set in rules, and this gets around that limitation.
Thanks!