cancel
Showing results for 
Search instead for 
Did you mean: 

Issue when looking up the "Initial" workflow queue

Tony_Kennard
Confirmed Champ
Confirmed Champ

Hi,

 

When doing a Unityapplication.Workflow.Queues.Find("Initial"), the queue that is returned has a lifecycle name of 'populate full name'.

 

Any suggestions?

 

Thanks

Tony

1 ACCEPTED ANSWER

Eric_Beavers
Employee
Employee

There could be a few things wrong here. What business problem are you trying to solve with the API?

 

Are you following the SDK samples similar to Workflow Ad-hoc Tasks (onbase.com) and creating a LifeCycle object?

 

 // Obtain the Unity Workflow class from your connected Application object Workflow.Workflow workflow = unityApplication.Workflow;    // Locate the Workflow life cycle that you wish to execute a task against. Workflow.LifeCycle lifeCycle = workflow.LifeCycles.Find("HR Lifecycle");  // Locate the Workflow queue inside the life cycle that you wish to execute a task against. Workflow.Queue queue = lifeCycle.Queues.Find("Initial Queue");

 

The other issue is going with the Default Queue name of "Initial". This is configured in OnBase Studio when creating new Lifecycles. Best practice for Workflow Developers:

https://support.hyland.com/r/OnBase/Workflow/English/Foundation-22.1/Workflow/Best-Practices/General...

 

"Create naming conventions for queues. Use prefixes when naming queues."

 

If this is not changed by the Workflow Admin/Developer then you might have dozens of queues named "Initial"

 

For example: If this is a Human Resources process for Recruiting then the Lifecycle might be named "HR - Recruiting" and the initial queue would be named something like "HRR - Initial"

View answer in original post

1 REPLY 1

Eric_Beavers
Employee
Employee

There could be a few things wrong here. What business problem are you trying to solve with the API?

 

Are you following the SDK samples similar to Workflow Ad-hoc Tasks (onbase.com) and creating a LifeCycle object?

 

 // Obtain the Unity Workflow class from your connected Application object Workflow.Workflow workflow = unityApplication.Workflow;    // Locate the Workflow life cycle that you wish to execute a task against. Workflow.LifeCycle lifeCycle = workflow.LifeCycles.Find("HR Lifecycle");  // Locate the Workflow queue inside the life cycle that you wish to execute a task against. Workflow.Queue queue = lifeCycle.Queues.Find("Initial Queue");

 

The other issue is going with the Default Queue name of "Initial". This is configured in OnBase Studio when creating new Lifecycles. Best practice for Workflow Developers:

https://support.hyland.com/r/OnBase/Workflow/English/Foundation-22.1/Workflow/Best-Practices/General...

 

"Create naming conventions for queues. Use prefixes when naming queues."

 

If this is not changed by the Workflow Admin/Developer then you might have dozens of queues named "Initial"

 

For example: If this is a Human Resources process for Recruiting then the Lifecycle might be named "HR - Recruiting" and the initial queue would be named something like "HRR - Initial"