Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Show Page Sections

Controlling the Structure

The structure that has been elaborated using the “Structure” is a fixed structure, meaning that every form property, every form and every Configuration Process node is always present (once) and always required.

The “Controls” step is used to dynamically control aspects of this structure, in order to specialize it for certain circumstances.

Concept

Multiple aspects of the Configuration Process structure can be controlled in order to make it more dynamic. For certain objects, you will be able to define whether it exists, if it is required, if it is visible, if it is updateable or even if it is nested.

Definition: An object exists when the existence rule returns true. An object which exists will take a part in the constraint propagation process.

Tip: The existence of an object is unrelated to the fact that it has been loaded (as in “present in memory”). Therefore, the existence of an object has to be considered as a way to determine
  • which part of the configuration MustBeAnswered by the user in order to successfully complete it
  • and which part of the business rules apply in a certain situation

    Definition: An object is visible when the visibility rule returns true. An object which is not visible will take a part in the constraint propagation process (if it exists).

    Tip: Visibility rules are very practical in collaborative configurations, in which different users will subsequently complete a configuration in different steps.

    Definition: An object which is required will need to be completed by the user.

    Definition: An object which is updateable can be changed by the user.

    Tip: Making sure that certain objects cannot be updated in certain situations is again very practical in collaborative configurations.

    Definition: An object which is nested can occur multiple times in the parent under which it has been created. These objects are said to be looped.

Control Configuration Processes and Forms nodes

The Controls step will allow you to setup the above-mentioned attributes.

FIELD REQUIRED DESCRIPTION
Exists Yes Determines whether the form or the node Configuration Process always exists or only in some circumstances. The existence can be given by a fixed value, or by a BRC Column-based.
Visible Yes Determines whether the form or the node Configuration Process is visible or only in some circumstances. The visibility can be given by a fixed value, or by a BRC Column-based.
Required Yes Determines whether the form or the node Configuration Process is required, not required, or only in some circumstances.
Updatable Yes Determines if the form or the node Configuration Process is always updatable or only in some circumstances. Can be given by a fixed value, or by a BRC Column-based.
Nested Yes Determines if the form or the node Configuration Process is nested. A nested form or Configuration Process is considered as being “looped”, and can be presented multiple times.
Min instances No Determines the minimum number of occurrences that will be necessary for a nested form or Configuration Process. Can be given by a fixed value, or by a BRC Column-based.
Max instances No Determines the maximum number of occurrences that can be created for a nested form or Configuration Process. Can be given by a fixed value, or by a BRC Column-based.

Control Form Property nodes

Controlling the form property again enables you to control the 3 parts of the answer given by the user: the value, the quantity and the comment.

Controlling the value

FIELD REQUIRED DESCRIPTION
Exists Yes Determines whether the form property always exists or only in some circumstances. Can be given by a fixed value, or by a BRC Column.
Visible Yes Determines whether the form property is visible or only in some circumstances. Can be given by a fixed value, or by a BRC Column.
Required Yes Determines whether the form property is required, not required, or only in some circumstances.
Updatable Yes Determines if the form property is always updatable or only in some circumstances. Can be given by a fixed value, or by a BRC Column.
Computed Yes Determines if the form property is computed or not, or in only in some circumstances. Can be given by a fixed value, or by a BRC Column.
FIELD REQUIRED DESCRIPTION
Immediate propagation Yes In the event that the form property is used as an optional alias in a macro, the flag “immediate propagation” determines whether the macro can be triggered without the form property being answered (immediate propagation: true) or not (immediate propagation: false). Can be given by a fixed value only. Note: If the flag “immediate propagation” is set to true, the “autoset” function (which will automatically attribute the last remaining value in a domain) is deactivated. Moreover, if the flag “immediate propagation” is set to true, the form property cannot be calculated.
  1. Controlling the quantity
FIELD REQUIRED DESCRIPTION
Exists Yes Determines if a quantity must be associated with the form property or not, or only in certain circumstances (BRC Column).
Visible [If Exists = yes] Determines if the quantity is visible or not, or only in certain circumstances.
Required [If Exists = yes] Determines if the quantity is required or not, or only in certain circumstances.
Updatable [If Exists = yes] Determines if the quantity is updatable or not, or only in certain circumstances.
Computed [If Exists = yes] Determines if the quantity is computed or not, or only in certain circumstances.
FIELD REQUIRED DESCRIPTION
Immediate propagation Yes In the event that the quantity is used as an optional alias in a macro, the flag “immediate propagation” determines whether the macro can be triggered without the quantity being answered (immediate propagation: true) or not (immediate propagation: false). Can be given by a fixed value only. Note: If the flag “immediate propagation” is set to true, the “autoset” function (which will automatically attribute the last remaining value in a domain) will be deactivated. Moreover, if the flag “immediate propagation” is set to true, the quantity cannot be calculated.
Tip: Note that by default the quantity does not exist.

Controlling the comment

FIELD REQUIRED DESCRIPTION
Exists Yes Determines if a comment must be associated with the form property or not, or only in certain circumstances (BRC Column).
Visible [If Exists = yes] Determines if the comment is visible or not, or only in certain circumstances.
Required [If Exists = yes] Determines if the comment is required or not, or only in certain circumstances.
Updatable [If Exists = yes] Determines if the comment is updatable or not, or only in certain circumstances.
FIELD REQUIRED DESCRIPTION
Computed [If Exists = yes] Determines if the comment is computed or not, or only in certain circumstances.
Immediate propagation Yes In the event that the comment is used as an optional alias in a macro, the flag “immediate propagation” determines whether the macro can be triggered without the comment being answered (immediate propagation: true) or not (immediate propagation: false). Can be given by a fixed value only. Note: If the flag “immediate propagation” is set to true, the “autoset” function (which will automatically attribute the last remaining value in a domain) will be deactivated. Moreover, if the flag “immediate propagation” is set to true, the comment cannot be calculated.
Tip: Note that by default the comment does not exist.

Controlling list-based form properties

The following attributes are only available for list-based form properties, which accept multiple answers.

FIELD REQUIRED DESCRIPTION
Min nbr of choices No Determines the minimum number of choices to be made in a multiplechoice list. This attribute can be given by a fixed value, or by a BRC Column.
Max nbr of choices No Determines the maximum number of choices to be made in a multiplechoice list. This attribute can be given by a fixed value, or by a BRC Column.