Bind Variables and Repeating Clauses

Clauses can include bind variables. The system resolves the binds and converts them to text when it generates the document.

Bind variables can be wizard binds or transaction binds. Wizard binds are user-defined variables that you create. Transaction binds can be linked to all source transactions. Transaction bind variables enable you to map values from transaction data into an authored document. For example, when the system generates a document, referencing the %%CONTRACT_ID%% bind variable can map the contract number from a purchasing contract transaction into a title clause.

Bind variables also have repeating attributes associated with them that are inherited by the clause or section in which they are used. For example, you can use repeating clauses for things such as an item description list by including the %%ITEM_DESCR%% bind variable within the clause title (or body). The bind variable %%ITEM_DESCR%% happens to repeat at level one because the item list is an immediate child record of the contract header, which is at level zero.

Therefore, you can define a clause to have this text: This inspection process applies to %%ITEM_DESCR%%. When generating a purchasing contract that has three lines, this clause could appear as:

1. This inspection process applies to 4 Piece Saltwater Fly. 
2. This inspection process applies to Rod and Reel Case Combo.
3. This inspection process applies to Travel Fly Rod.

In addition, you can nest repeating-level clauses and sections. For example, a dependent clause can be assigned to an existing parent clause that repeats level two data, such as contract milestones. This is a child record to the procurement transaction contract line in the parent clause. When nesting repeat structures, the system uses the proper child repeating clauses with the immediate parent by checking the level and key structures of each bind variable.

Note:

Proper setup of nested repeating structures requires some technical expertise. PeopleSoft Supplier Contract Management provides a set of transactional binds for source transactions. Wizard binds are less complex and do not use repeating structures, so they are always at a level zero.

A clause can stand alone, be used as a dependent clause, or be used as an alternate clause. Dependent clauses are associated with a primary clause. Alternate clauses are used instead of a primary clause.