nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Workflow Initiation | STAGING Area

Vivek552

Hi All,

I am planning to initiate workflow from staging area, but when i do so, i am getting these additional fields in my initiation screen.
1) Areaowner
2) Workarea

I am not able to set these thorugh form API, since they are not getting available as IWItem.

Also i tried require_workarea="false" in availablemodels.xml but with no luck. I am still getting those two fields in my initiation screen.

Can you please help me how to resolve this error, since i don;t want users to enter these two values, either these should be disable or should be hidden or should be assigned through formAPI.

Please help.

Regards:
Vivek

Find more posts tagged with

Comments

Adam Stoller

Hi All,

I am planning to initiate workflow from staging area, but when i do so, i am getting these additional fields in my initiation screen.
1) Areaowner
2) Workarea

I am not able to set these thorugh form API, since they are not getting available as IWItem.

Also i tried require_workarea="false" in availablemodels.xml but with no luck. I am still getting those two fields in my initiation screen.

Can you please help me how to resolve this error, since i don;t want users to enter these two values, either these should be disable or should be hidden or should be assigned through formAPI.

Please help.

Regards:
Vivek

Are you actually planning to have users initiate a workflow in the staging area? Why not initiate it the workflow in the workarea and just set the task(s) areavpath to the staging area (you might have to use a Configurable Variable in the model, default it to IW_WORKAREA, and then use simple regex in custom_instantiation.cfg to switch it to the staging area.

Note - any task that operates in the staging area MUST be marked as readonly.

Vishakha

Have you selected $IW_WORKAREA and $IW_USER as the values for the areaVpath and Owner attribute respectively for every task in the workflow?
If still you are getting the fields on the instantiation screen, it means that your workflow is not able to get these system variables.
We had a similiar problem in some other scenario and the below solution worked.
If it is ok for you to hard code the path try the following:
1. Assign a script variable to AreaVpath and Owner for every task in the workflow.
2. In the value of the script variable hard code the value that you want, again for every task.

Check if this works for you and surely reply if it does!!!

nipper

I would rethink this requirement and execute the workflow out of the workarea.

What is the use case ?

JoinDataSet.rptdesign

Vivek552

Thanks for all your replies.

I have not checked the below solutions, since i have doubt in my appraoch itself.

Saying that, can you please tell me if
1) it is possible to submit files to workflow from STAGING?
2) If yes, then what is the real purpose of AreaVpath in that screen? My assumption is it represents workarea.

If we have to assign workarea when trigerring workflow from STAGING, then i guess its no point initiating workflow from STAGING.

Please clarify.

Regards:
Veera

Adam Stoller

...

If we have to assign workarea when trigerring workflow from STAGING, then i guess its no point initiating workflow from STAGING.

Please clarify.

Regards:
Veera

Perhaps you should clarify - what is the reason you expect someone to be within the staging area when initiating a workflow? That is definitely not a location that most users find themselves in when initiating a workflow.

Are you sure you want a workflow? Perhaps you just want a custom menu item (if all you want to do is select some files in the staging area and deploy them, with no reviews, etc.)

Vivek552

yes, you are correct and we are using this workflow for emergency workflow, which will just deploy files from staging.

So, are you proposing not to go with workflow initiation screen to resolve this problem? can you please suggest any other solution please...

Regards:
Veera

Adam Stoller

yes, you are correct and we are using this workflow for emergency workflow, which will just deploy files from staging.

So, are you proposing not to go with workflow initiation screen to resolve this problem? can you please suggest any other solution please...

Regards:
Veera

If there is no review involved and all you're looking to do is select N files in the staging area and deploy them - then I've already provided the suggestion: custom menu item.