Project and Portfolio Management Practitioners Forum
cancel

Tokens not resolving in execution step

Highlighted
b460
Super Contributor.

Tokens not resolving in execution step

Hi,

We have a request that has a field which is autmoatically populated with the result of a rule that is triggered.

When we try to use this field in an execution step by referencing the token to compare values it seems that the token is always null.

Does anyone know why when a field is populated from the result of a rule, its token is null and if there is anyway to get around this so the token contains the correct token so it can be resolved correctly?
12 REPLIES
Mahen M
Acclaimed Contributor.

Re: Tokens not resolving in execution step

can you attach the snap of the execution step?

Regards,
Mahendran M
b460
Super Contributor.

Re: Tokens not resolving in execution step

Please see the attached screenshot of the execution step.
Jim Esler
Acclaimed Contributor.

Re: Tokens not resolving in execution step

What does the rule look like?
shygirl
Super Contributor.

Re: Tokens not resolving in execution step

Have you tried capturing if the tokens have values before the request passed through the exection step?
b460
Super Contributor.

Re: Tokens not resolving in execution step

Please see attached a screenshot of the rule.

The fields in the dependencies section are populated in the following way:
- Estimate To Complete: automatically by another rule.
- Actual Expentiture To Date: manually by user input.

The rule the adds these 2 fields together and puts the result in the Estimate At Completion field.

What seems to be happening is that beacuse the Estimate At Completion field is populated by a rule, its value is not being stored in the token.

Is it possible the fields that get populated by rules, dont populate the token associated with it? How could I get around this so the token gets populated?
Jim Esler
Acclaimed Contributor.

Re: Tokens not resolving in execution step

The token is just a way to get the field value. If the field has a value, the token will get it. There are a couple of other possibilities for not getting values here:

1. Rules do not 'cascade'. If a field is changed by a rule, the change will not trigger another rule. Rules are triggered only when the field is changed by a user. You can get around this by adding a dependency on this rule for the field that triggered the change to the other field.

2. We recently upgraded to 7.5 and have discovered that now rules will not change a field if the user triggering the rule does not have access to the field. This is a change from 6.0.
Linda Hauck
Respected Contributor.

Re: Tokens not resolving in execution step

To Jim:

Regarding your statement about when you upgraded to 7.5 and then the rules wouldn't fill fields that a user doesn't have access to.
This would be very bad for us! Did you find a solution to this? We are getting ready to upgrade to 7.5->8.0

thanks!
Linda

Jim Esler
Acclaimed Contributor.

Re: Tokens not resolving in execution step

The problem concerns access based on field level security. We just identified the problem yesterday and do not have a resolution. We have seen the issue only with 7.5. It did not work this way in 6.0. We did not use 7.1 in production so I have no idea how it behaves. We have not looked at 8.0 yet.
Erik Cole
Acclaimed Contributor.

Re: Tokens not resolving in execution step

Jim, what patch level are you on? I can't reproduce this in 7.5 sp 2 or 8.0 sp1...?
Jim Esler
Acclaimed Contributor.

Re: Tokens not resolving in execution step

We are running 7.5 SP6 with a couple of hot fixes related to validations using command with delimited output / multi-select / short list.
b460
Super Contributor.

Re: Tokens not resolving in execution step

OK, back to the original post, i'll re-explain the issue to see if it comes across clearer.

So looking at the execution step (first attachment in thread).

The [REQD.P.ESTIMATE_AT_COMPLETION] field is populated by a rule and the [REQD.P.APPROVED_BUDGET] field is populated by a rule.

When the request gets to the execution step, it is always going to the 'UNDER_BUDGET' case.

If I populate these fields manually it works fine. Any ideas?
Erik Cole
Acclaimed Contributor.

Re: Tokens not resolving in execution step

b460, I think the most likely case is what Jim said earlier (#1 @ Jan 27, 2010 16:34):

If ETC is updated by another rule, then this rule will not be triggered and EAC will not be updated. The only thing that will trigger this rule is when one of the fields is changed directly by a user. Thus, if ETC is updated by another rule _after_ AETD this rule won't be fired.

Likewise, if someone updates the AETD field and there is not already a value for ETC, this rule will result in a NULL value for EAC.

Having said that, can you show us a snapshot of the request page with your test values in all the fields and tell us what result that execution gives for them?