Approval Process on Custom Object Failed

[former_member400589]

Hi experts,

I have created a customized BO with approval process defined. Currently, I have 3 problem with this.

1. I have errors while submit the instance to approval as below. The error message is "Process definition exists with configuration error Task type exists with instantiation lock"

2. I tried to modify the approval process, but the system prevent my changes with errors. "Cannot maintain the process; Instantiation lock is set for task type YI676K31Y_APP2_APP"

3. If I want to have a multi choices in the work distribution dropdown box, just like what we have in the Approval Process for Contract like below, how to achieve this?

Thanks for your help.

BR

Kevin

[liekensp33]

Dear,

Can you please share or provide me with a blog or tutorial on how to create this approval flow on a custom object?

We have the same request to create an expense request with approval for one of our customers.

Please PM me on peter.liekens@delaware.pro

Kind Regards

Peter

[former_member591589]

Hi!

We have the same problem. After making many business configuration deployments succesfully the approval process still raising the error: "Cannot maintain the process; Instantiation lock is set for task type...". It seems that there is some backend issue that must be fixed. I created an incident and they are trying to fix it performing a workspace update from backend.

Thanks!

[former_member263502]

Hi,

Due to some technical background processes, it takes some time to deploy the business configuration. Alternatively try scoping the solution in Business Configuration work center.

Thanks & Regards,

Hindu

[former_member545775]

I have the same problem 1 & 2 in business by design

i deployed business configuration more than once successfully and still the same issue

any help please ?

[former_member518580]

Hi Kevin,

Issue 1 & 2 occur when there is a change in the design time data in the approval process related files. In order to keep things consistent, approval task type is "Instantiation locked" until the changes are deployed into the workspace. This can be resolved by updating the workspace or by doing "business configuration deployment" in the cloud studio.
Coming to the issue 3, if my understanding is right, you are expecting more approvers to be visible in the "Work Distribution" dropdown. The approver fields that are visible in the drop down for custom approval process are the ones that are created in the BO of EmployeeID type. If you want more approver fields, please add the required ones in the BO definition and update the approval process file. Remember to deploy these changes to avoid task types being "instantiation lock".

Hope this answers your questions.

Best Regards,
Sasi.

[former_member400589]

Hi Sasi,

Thanks for you comments.

Regarding the issue 3, yes we want there be more options to choose. For example, we want the requestor's line manager to approve the request, but we could not fix the employee id as there will be multi organization units, we want the system determine the approver automatically. Do we have to check the line manager while submitting to approval?

I have go thru the document and scn, but failed to find how to realize this. Thanks for providing some hints on this.

BR

Kevin

[former_member518580]

Hi Kevin,

There are a couple of ways to achieve this.
1. Create a BO field for line manager of EmployeeID type and fill this field with line manager's id to whom you want the notification to be sent. You need not hardcode one particular employee id.

2. Again, create a BO field for line manager. In the UI designer, add an OVS (that has the line manager) to this field. During BO instance creation, the creator can choose from the list of users available in the OVS.

Thanks & Regards,
Sasi.

[former_member545775]

I have the same problem 1 & 2 in business by design

i deployed business configuration more than once successfully and still the same issue

any help please ?

[former_member400589]

the issue 1& 2 is now solved, due to the "Software Upgrading" of C4C system.