Establishing Context

vinsnash

When I select an instance from a standard query result list for edit is that instance written to context? If not how do I make that happen so I can use attributes of the instance in a rule to be executed when creating a reference for that instance?

Thanks for the help

Vins Nash

aware_support

Yes, it is placed into the Context. You can define an operation that, for example, starts a process. You can define an object displayed by the query to be a parameter for the process. This object will be automatically placed in the context for the process to use.

vinsnash

I have a reference attribute "PrimaryContact" in BO NSCPers. I select an instance of NSCPers from a query result for edit. The frame for "PrimaryContact" is there and I select the "Add" "+" button which brings up the form for the BO "PrimaryContact". I have a yes/no attribute in "PrimaryContact".

I want to use a rule:

If PrimaryContact is NEW and PrimaryContact.Same = YES

Then PrimaryContact.Address = NSCPers.Address

When I save the rule this error pops up:

"Possibly wrong identifier NSCPers is used in path NSCPers.Address in rule PrimaryAddressRule. Do you want to proceed .....?

My intent is to auto fill some fields of PrimaryContact with data from NSCPers. What's wrong here?

Thanks for your help

vinsnash

This is not working for me.

Once I have selected an instance of a BO for edit from a query out put list how do I reference attributes of that BO in a rule applicable to a new reference I create.

The references are for varying contact names that may have the same address as recorded in the BO instance selected from the query and I want to populate those attributes in the reference automatically.

Thanks for all the help. Couldn't do this without it.

BobK

Here are 2 possible solutions.

Solution 1:
You will need a matching attribute in PrimaryContact pointing back to NSCPers. For the purpose of this example, I will call it MyNSCPers.

Your rules could then be:

If PrimaryContact is NEW and PrimaryContact.Same = YES
Then PrimaryContact.Address = PrimaryContact.MyNSCPers.Address

Solution 2:
No matching attribute is needed, but this may not meet your requirements exactly.

Have a process that creates the PrimaryContact and allways sets the PrimaryContact.Same attribute to 'Yes" and the PrimaryContact.Address to NSCPers.Address. If the addresses need to be different, the user will need to manually change them.

Here are the details

Create a process with the following actions:
ENTER NEW PrimaryContact WITH PrimaryContact.Same='YES', PrimaryContact.Address=NSCPers.Address

In your NSCPers form, for the PrimaryContact attribute where you check Generate "Add New" button', go into Settings... select custom implementation and select the above process.

vinsnash

I used #1. I kept reading the material on references and I don't think I saw anything specific on syntax regarding referenced attributes. i.e. having to use the reference name in the full attribute name. I never would have guessed that figuring that selecting an instance of an object from a query result list would put that instance in the context and allow use of its attribute names directly.

Thanks for the help.

Vins Nash