The Sql Node in RSA Workflow is excuting corretly for few users and for few users it is not.Kindly help in resolving he same.
The Query am trying to run is:
SELECT CUS_ATTR_USER_CAS_12 as costCenter,
'${access_request_cri_meu_CUS_ATTR_USER_CAS_2}' as managerID,
'${access_request_cri_meu_CUS_ATTR_USER_CAS_6}' as userID,
CUS_ATTR_USER_CAS_4 as wrktype
FROM avuser.T_Master_Enterprise_Users
WHERE USER_ID ='${access_request_cri_meu_CUS_ATTR_USER_CAS_6}'
Your help is much appreciated.
The Version we are running is Version: 6.9.81259 P02
We have built a workflow to assign a particular attribute to the user.Based on the Output of the SQL node in workflow a decision node will be followed.According to query below managerid ,userid,wrktype values are populating correctly for few change requests (particular user in where clause) for other it is not due to which decision node is redirecting to some other flow not sure what is the issue.
Workflow is not failing but redirecting to a different path than expected path.
SELECT CUS_ATTR_USER_CAS_12 as costCenter,
'${access_request_cri_meu_CUS_ATTR_USER_CAS_2}' as managerID,
'${access_request_cri_meu_CUS_ATTR_USER_CAS_6}' as userID,
CUS_ATTR_USER_CAS_4 as wrktype
FROM avuser.T_Master_Enterprise_Users
WHERE USER_ID ='${access_request_cri_meu_CUS_ATTR_USER_CAS_6}'
I would recommend running a modified version of the query against t_master_enteprise_users table to list out all users that have user_id=CUS_ATTR_USER_CAS_6. Cross-referencing this list with the users that do not seem to work appropriately in the workflows should give you a path to debug forward. The syntax of the query is fine so I would suspect that the scenarios that do not work are related to users that do not satisfy the query.
If you need more insight, please include a screenshot of the workflow along with what is being evaluated in decision nodes using the variables captured in the query above.
Can try
1) Check the database ID for these attributes in the User Attribute {Admin - Attributes - User}. If CAS2 is mapped to managerID and check for other attributes.
2) Directly fetch the data from the columns of t_master_enterprise table or pv user based on your where clause WHERE USER_ID ='${access_request_cri_meu_CUS_ATTR_USER_CAS_6}'
How are you evaluating the decision node? More details will help
Thanks Boris,Manu,Pooja for your time.
Hi Manu and Pooja Please find the details:
I did ran a query as you suggested against table t_master_Enterprise_users all users are populating correctly through SQL DEVELOPER.
The decision node here will check whether the user is Employee or Not if Employee 'T' it has follow the path mentiond.But It is evaluating to 'F' and Workflow is completing.
Userid from Access Request is not populating properly in where clause.That is why values are not evaluating as expected.
so the decision is based on CUS_ATTR_USER_CAS_4 attribute and it has to follow the path based on the value - Employee.
Can you please check
- what is the Database ID of the UserID
- what is the value being calculated for the access request variable (UserID) and value of other attributes which you are using to make the decision [Run Time data]
I suggest to clarify the scenario by providing additional information.
For example:
What version are you running on?
What does it mean not working correctly for some users? Are the results not as expected or the workflow fails?