Created a package in wise 6.2, next in Directory Table created string to set a Default directory to use it in CA which is sequenced in Normal Execute immediate/Defferred with in script option: Deferred Execute- system Context.

But is there when n script option: immediate Execution

During upgrade the property is not there using: mgbox session.property("INSTALLDIR1"), gives an empty box.

what can i do to have the property, once my CA runs.

Thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
During deferred execution only a limited set of properties is available by default (ProductCode, UserSID and CustomActionData) so you'll need to cast your property value so it's available in deferred execution custom actions.

Read this article for a run-through of how to do this.

PJ
Answered 10/27/2011 by: pjgeutjens
Red Belt

Please log in to comment
0
Thank you pjgeutjens for the reply and the link...

I follow the two steps on page 2, but the value of "CustomActionData" property, is blank and not set to the [INSTALLDIR1].

what i did is created a Set property CA called ABC in that set the property to the deferred CA example "DefCA" and the value to [INSTALLDIR1], seq. in Normal execute immediate placed before "DefCA". and in the "DefCA" i used "CustomActionData" instead of [INSTALLDIR1].

am i doing something wrong?
Answered 10/28/2011 by: Netrock
Orange Senior Belt

Please log in to comment
0
Ok i found where the problem was. i tried before to place the CA In UI to see if that makes a different, next i changed to Execute Deferred, But Wise kept the CA in UI mode and execute Deferred.....!!!

Now it is working thanks for your help. really appreciated!
Answered 10/28/2011 by: Netrock
Orange Senior Belt

Please log in to comment
0
This bug has been around in Wise since God Knows When. It occurs when you move CAs around using the UI.

Essentially, the actual sequence number doesn't get updated. I always use a prefix to my CA names to indicate where it occurs (or should occur!) so that, if this happens, I can see straight away in the relevant tables. Simply editing the sequence number is all that's required to restore sanity.
Answered 10/31/2011 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity