Difference: 520DesignXferChildren (2 vs. 3)

Revision 32013-07-19 - AlKalter

Line: 1 to 1
 
META TOPICPARENT name="APPX520Features"

Design Transfer Children

Line: 22 to 22
 
  • If you are transferring a specific Automatic Child, the 'Auto Child Seq' is optional. If not provided, it will use the same number as the source, otherwise it will be transferred to the specified seq no.
  • If you are transferring all Optional Children, they will be copied to the specified Image (you must choose a different process or frame in this case).
  • If you are transferring one Optional Child, the 'Option No' field is optional. If not provided, it will use the same number as the source, otherwise it will be transferred to the specified Option No.
Changed:
<
<
You cannot supply both an 'Alternate Image/Option No' and 'Auto Child Seq', you can only transfer either Optional Children or Automatic Children, not both at the same time.
>
>
You cannot supply both an 'Alternate Image/Option No' and 'Auto Child Seq', you can only transfer either Optional Children or Automatic Children, not both at the same time. And you cannot mix Automatic and Optional children on a transfer.
 

Comments:

Read what other users have said about this page or add your own comments.

Changed:
<
<

Question - Will the transfer include Pre-Invocation and Post-Invocation event points. GUI Attributes, and Child Constraints?

>
>
Note - The transfer will include Pre-Invocation and Post-Invocation event points, GUI Attributes, and Child Constraints.
  -- AlKalter - 2012-07-30
<--/commentPlugin-->
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback