we have created, in the our case Order, a new flow 'SOSPENSIONE_FWB' on ruleset FFB:01-03-01 and we have changed it on rulest FFB:01-04-04. When the user get the Order (on the case worker) the application returns error **Failed to find a RULE-OBJ-FLOW with name 'SOSPENSIONE_FWB' that applies to 'FF-FFB-Work-Order'.There are 2 rules with this name in the rulesetbase on ruleset (FFB:01-04-04,FFB:01-03-01). Current RulesetList FFB:01-02, FFBInt:01-02, etc. (in attachment more details).
The Access group assigned to the user is correct and point to FFB:01-04-01 application with ruleset FFB:01-04. From Profile the rulesetlist is correctly FFB:01-04, etc.
This error occurs only on some orders. Could you help me?
I worked on a case once for a similar issue. While testing, I came across this scenario where the error was saved in the work object. I was working on 7.2.1 at the time.
I created a new application with an access group called TestApp:Administrators.
I created a work object and routed it to my worklist.
I confirmed I could open the assignment successfully with the TestApp:Administrators access group.
I removed the access group from my operator record, logged out, and logged back in.
When I tried to open the same assignment from my recents list, I received an error "Failed to find a 'RULE-OBJ-FLOW' with the name 'CREATE_FLOW' ..." since I no longer had the appropriate ruleset in my ruleset list.
I then re-added the TestApp:Administrators access group, logged out, and logged back in.
When I attempted to open the assignment again, I still saw the error related to the flow with a button to 'Clear Error'. I could clear the error and submit without issue.
In your case, is it possible that a user or agent without those rulesets tried to access the work object and that is when the error was saved? If you clear the error, is the user with the proper ruleset able to process the work object successfully?
The user can click on Clear Error and can continue to work the order. In the clipboard I don't see error on the pyWorkPage but I see pxAssignStatus = Error : Rule-Obj-Flow not found on flow SOSPENSIONE_FWB (details in attach).On the tracer I see that application reads others rules on FFB:01-04.
Sounds like it could be similar to the scenario I mentioned then. Could someone with a different access group have tried to open the assignment from the worklist, or maybe there was an agent that tried to process it?
I understood!The user opened the work object before with AG that point to FFB:01-02 and application saved error message. After he opened the same work object with AG that point to FFB:01-04 and see the error message "flow not found". I have reproduced the scenario in the test environment and the user has confirmed this scenario.