First off, in the release activity, under Resource(s) to Release, you need to choose one of the standard options like Last Acquired or First Acquired.
Second, when using resources in numeric mode, if you assign everything to the same label and the acquire quantities are the same, there's no guarantee that they will be returned in the order that you desire. The result is that whether you choose Last Acquired or First Acquired, the Release1 activity will always release back to Resource1. The solution is to simply assign the acquired resources to different label names, i.e. the first Acquire should assign the acquired resource to Label: resource, while the second Acquire should assign the acquired resource to Label: resource1. The releases should subsequently release from the label associated with the corresponding acquired resource.
We have tried to find solutions for this but we haven't felt like any of our proposed solutions were robust enough to warrant implementation. The under-the-hood logistics are a bit complicated. The token keeps track of which resources have been acquired onto which labels and what their quantities are, but when a single label has been assigned two different resources with the same quantity, it becomes difficult to decipher which one is the best one to release.
It looks like you tried to reference the resource object you wanted to release back to in the Resource(s) to Release field. Perhaps we could add that as a feature, where if you return a reference to a resource object, it will release whatever has been acquired from that resource on the given label.
|
