Cannot save Initiator configuration based on a Custom Attribute

[former_member325725]

Hi Experts,

We usee SAP GRC CUP 5.3 SP8 P1.

We are trying to route new/change requests to a specific workflow based on a the value of a custom attribute(User Group) set up with the initiator.

The initiator condition is as follows:

Request Type New Account OR

Request Type Change Account OR

User Group XYZ AND

And all other New/Change requests that do not have a value 'XYZ' for the user group should take a different WF path:

So the initiator would be like:

Request Type New Account OR

Request Type Change Account OR

User Group XYZ NOT

Unfortunately, i cannot get this saved as above and the trace says:

com.virsa.ae.configuration.bo.WorkflowInitiatorsBO : saveInitiator() : : Exception occured while saving Workflow Initiator: Attribute does not exists for the given workflow type

[EXCEPTION]

com.virsa.ae.dao.DAOException: Attribute does not exists for the given workflow type... [see details]....

Full Message Text

com.virsa.ae.configuration.bo.WorkflowInitiatorsBO : saveInitiator() : : Exception occured while saving Workflow Initiator: Attribute does not exists for the given workflow type

[EXCEPTION]

com.virsa.ae.dao.DAOException: Attribute does not exists for the given workflow type

at com.virsa.ae.dao.sqlj.WorkflowInitiatorsDAO.update(WorkflowInitiatorsDAO.sqlj:514)

at com.virsa.ae.configuration.bo.WorkflowInitiatorsBO.saveInitiator(WorkflowInitiatorsBO.java:681)

at com.virsa.ae.configuration.actions.WorkflowInitiatorsAction.saveInitiators(WorkflowInitiatorsAction.java:1198)

at com.virsa.ae.configuration.actions.WorkflowInitiatorsAction.execute(WorkflowInitiatorsAction.java:261)

at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)

at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(AccessController.java:219)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

But if i change the attribute from the custom : User Group to a standard one like : Functional Area, it gets saved successfully.

But i cannot use this attribute as we get the request submitted through a web service which is not sending in this value.

Is this supposed to work for custom attributes as well? I hope yes, as I can get the custon attributes listed for initiator config. But i also notice that none of these attributes are listed in the Attributes(Configuration -> Attributes screen)

I know SP9 is offering User Group attribute by default, so it could be possible there, but any ideas why it's failing with SP8?

Thanks,

Anil

[Former Member · Accepted solution]

Oh and if body wanted ti use a custom field to trigger user defaults, that do stopped working after 5.3 SP8.1. I am waiting for SAP to inform me if that too is a bug.

[Former Member · Accepted solution]

Yes, it seems this is a bug. I remember it used to work till SP5 and I did not test it after that. Open a message with SAP to confirm if and when they are fixing this.

Alpesh

[Former Member]

We also hit this issue. We were using a custom field to do this and it worked fine in 5.2 but after the upgrade to 5.3 SP 8.1 it stopped working.

We opened an OSS message and was informed that this is a bug and will be fixed in SP11.

[former_member325725]

We got a work around suggested from SAP as to recreate the initiator or create a new one. And it worked We were trying to edit an existing one where we ran into issues.

SAP is planning for a fix the issue in SP11

Regards,

Anil

[Former Member]

Anil,

Is this a custom field and while creating if you have set it to 'Yes' for workflow and related it to request then you should be able to set it up for workflow. I don't think there is issue with the attribute. I think CUP does not like the condition criteria you are setting.

Can you provide your custom field config and also the criteria you are trying to set in the initiator?

Regards,

Alpesh

[former_member325725]

Yes Alpsh, this is a custom field. And CUP surely doesn't like the config i'm trying

Custom Filed Settings:

Workflow - Yes

Mandatory - Yes

Applicable to - Request

Field Type - Dropdown

And i'm pulling the user group from SAP system.

Following is the initiaotr config I have problems in saving :

Request Type New Account OR

Request Type Change Account OR

Action of Role ADD AND

User Group XYZ AND

But if i replace the User Group (custom filed) with Functional Area (standard req attribute), i can save the initiator and for the second initiator i want to set up as :

Request Type New Account OR

Request Type Change Account OR

Action of Role ADD AND

User Group XYZ NOT

Why this could fail if it can show the custom filed as an attribute for setting up the initiator and i'm using the same logic as for a standard attribute (like Functional Area) . I also tried if i can make use of the other standard attribute 'Business Process' which also got saved with the above logic. but failed in delivering the functionality I'm trying for.

Hope u have some ideas as always

Thanks,

Anil