cancel
Showing results for 
Search instead for 
Did you mean: 

Unity Script not executing?

Brian_Bartolazo
Confirmed Champ
Confirmed Champ

I am having an issue with having an Unity script executing in a workflow in a context when a document is added through a DIP Process.

I have a document that is set up for a lifecycle and the first thing it does is executes a "Run Unity Script" action that points to my unity script with is a IWorkflowScript. When uploading a document through the client, the script executes fine and the results are expected.

However, these kind of documents will be coming into the system via DIP. I have the DIP configured to send documents into the workflow, which it is doing perfectly fine. The problem is, when it hits the task, it doesn't look like it actually runs the script. I have "Log Execution" checked on the Run Unity Script task which shows it's at least hitting that action but the first item in my Unity Script is writing to the Diagnostics log, but nothing appears.

I've tried it with other types of Unity scripts such as "IClientWorkflowScript" but no luck. The current IWorkflowScript works perfectly fine when testing through the client, it just does not seem to run the script when the document is imported via DIP.

I know there are tons of different kinds of Unity scripts you can set them as, but I didn't see any that sounds like it would work.

Any thoughts?

Thanks!

1 ACCEPTED ANSWER

William_Howell
Star Contributor
Star Contributor

Is the Unity Script call running as System Work? If so, try having DIP send documents into the queue with no System Work and then have a Core based timer (Hyland Workflow Timer Service) execute the logic currently in System Work.

This will also speed up your DIP processing since DIP won't have to spend time on workflow logic.

Bill

View answer in original post

3 REPLIES 3

William_Howell
Star Contributor
Star Contributor

Is the Unity Script call running as System Work? If so, try having DIP send documents into the queue with no System Work and then have a Core based timer (Hyland Workflow Timer Service) execute the logic currently in System Work.

This will also speed up your DIP processing since DIP won't have to spend time on workflow logic.

Bill

Mike_Schaefer
Star Contributor
Star Contributor

Alternatively, the client running the DIP process itself can be configured to run in Core-based mode; then, when the Commit is performed, it would run the Unity Script.

Eldo_Joseph1
Champ in-the-making
Champ in-the-making

Try to create a rule to check enviorment first the on true and false condition call unity an vb script logic. Put the rule under System task or Ad-hoc task. Give a try!  -Eldo