Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resource Selection extension #6

Open
GeoffHook opened this issue Dec 1, 2014 · 1 comment
Open

Resource Selection extension #6

GeoffHook opened this issue Dec 1, 2014 · 1 comment

Comments

@GeoffHook
Copy link

In many business processes the particular resource instance that is selected for a task must stay with that piece of work (token) through later steps. This named resourced could be stored as an attribute of the token and referred to in a subsequent resource selection expression.

This implementation could also be used to stop a particular resource being used at a later step to work on a token. This functionality is sometimes required to make sure a quality check is performed by a different resource instance to the one that did the work, even though they maybe both doing the same role.

@SimonRinguette
Copy link

SimonRinguette commented Jul 13, 2016

One possible solution would be to introduce an evaluation moment for the property (evaluateAt) and introduce a getCurrentPerformer() method to xpath.

<ElementParameters elementRef="Task1">
    <ResourceParameters>
        <Selection >
            <ExpressionParameter value="orResource(getProperty('storedFromA') , getResource('finance', 2) | getResource('sales', 50))" />
        </Selection>
    </ResourceParameters>
    <PropertyParameter>
        <Property name="storedFromA" evaluateAt="end">
            <ExpressionParameter  value="getCurrentPerformer()"  />
        <Property>
    </PropertyParameter>
</ElementParameters>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants