Behavior of workflow in Contributor?

[dharav]

Hello All

In contributor, everyone has submit the data and all level turn out to be locked. I did rollover now and open next month. In contributor still workflow shows locked.
I want to know that how can we change the status of workflow as open from locked status after rollover. (In EP, When we do rollover, all the submission made (locked status) is getting open for input for the users. How could we achieve that in tm1?)

Let me know if you require further information on it.


Your prompt inputs would highly appreciated

Thanks

Dharav

[declanr]

What do you mean by you did a rollover?

To reset security for an entire application you can tick that application in the pmpsvc portal and press the "reset application" button up in the top right of the window.

[dharav]

Suppose,

All user has submitted their data for the month of may in contributor. Every node in workflow is in locked status. Now, I want each node to be available (status) for user to input Jun month data.

I want to know, How could i turn those locked status in to available status for user to input data for next month?


If i do reset the application than all submitted data would automatically commit and would get the original workflow? What about the sandbox that user has saved?

Let me know if further information required to understand the issue.

Thanks

Dharav

[jcortes]

Hi, clic on reject does not working?.. see atachment.

[dharav]

Appreciate Your Inputs

In you example Jcortes

I know how to reject chicago. Now assume you have following city under Illinois Region

Chicago
XYZ
ABX
PQR
MNQ
UVW

Now i want to reject all the submission made by all city under Illinois Region but without clicking reject button individually on each city. Is there a way to reject all submission from region or by a single click.

I have a consolidation having more than 76 elements. Now it is cumbersome for reviewer to reject each city individually. It consumes extra time. Can we get rid off this as of now?


Thanks

Dharav

[declanr]

Dharav,

Your earlier post suggested that you wanted to reset the whole application to an unlocked state, if this is still the case - did you press this button as my previous post suggested you should?

Your previous post however suggests that you perhaps just want to reject all submissions under a certain node, is that actually the case instead?

[dharav]

Declanr

Yes it is the case. I just want to reject submission. I don't want to reset application because it resets all workflow not specific region work.

Thanks for your Input

Dharav

[declanr]

The TI that rejects a submission is based on parameters passed into it so it wouldn't take much to build an extra TI that loops through all the children of a given element and executes the reject TI for the children. This wouldn't appear on the application screen but could either be ran by an administrator or placed in an action button on a websheet that is part of your application, allowing the users to execute it.

[dharav]

Declanr

Just correct me if flow is not correct

1) I should use the parameter for each region

2) I should write TI which loops the metro level on the basis of passed parameter region

3) Now write TI process to reject the each metro level that we looped through

4) Run the TI.

Now each time i just need to execute the process by using the parameter region only. Am i right?


Thanks

Dharav