Learning About Conditions

Objective

After completing this lesson, you will be able to describe the conditions associated with the preparation of main agreement.

Preparing the Main Agreement

A flow diagram illustrates the process of preparing the Main Agreement.

Conditions

  • Conditions are logical constructs which can be used to determine the visibility of SAP Ariba Contracts templates or if certain documents, tasks, or team members are included in a contract workspace.
  • May also be used in contract documents to determine which section and clauses will be used.
  • Allows Main Agreement template to be used in multiple scenarios, making it very flexible.

In SAP Ariba Contracts, conditions can also be used on sections and clauses within Main Agreement templates to determine which are included in a contract workspace. This allows a single Main Agreement template to create workspaces with different Main Agreement content based on information entered by the creator of the workspace. This can greatly reduce the number of Main Agreement templates required. The same is true of Contract Addendum documents.

Types of Expressions

Five types of expressions can be associated with conditions:

When creating expressions, the system offers expressions that can be used to help define these expressions. These allow for administrators to create expressions that meet complex business requirements.

There are five types of expressions that can be associated with conditions:

  • Field Matches - when a field matches a specific value, the condition is true, e.g. Region = USA.
  • Reference to Condition - reference to another existing condition. For example, if Region is True and Department is Corporate. Region is True is the reference to the already existing region condition.
  • All of Expressions - group multiple field match expressions together in a set. When all fields in the set match the specified values, the condition is true.
  • Any of Expressions - group multiple field match expressions together in a set. When at least one field in the set matches its specified value, the condition is true.
  • None of Expressions - group multiple field match expressions together in a set. When none of the fields matches its specified value, the condition is true.
Types of Expressions are displayed. Details are provided in the paragraph above.

Questions

Questions used in conjunction with conditions can be used to define Main Agreement content from a given template during project creation. Based on the answers to questions, the system includes the appropriate sections and clauses in a new workspace created from a template.

In addition to simply matching fields, conditions may be built around responses to questions that the contract author answers in the creation wizard.

The Visibility Conditions for the question determine when the question is displayed to workspace creators.

Is answer visibility conditional indicates whether or not certain answers will be displayed based on specific conditions.

Can answers set project fields allows you to select fields that will be set to a specified value when an answer is chosen.

Note

SAP Ariba Best Practice: A good way to force users to select a response is to add an answer with the text Select an answer, set it as the default answer, and then require that the answer must be changed.

The default answers are always yes and no, but you can change the text and add as many additional answers as you like. You can reorder questions by dragging and dropping them to different positions on the list. The Defined Condition column allows you to enter the name of the condition that will be true when a particular answer is chosen. It is a best practice to keep the names short.

Hint

When creating your conditions and assigning conditions names, keep the following in mind. The Test Conditions box displays the conditions in alphabetical order. So if you have a condition with several values, you should begin the condition name with the same word so they appear together in the Test Conditions box. E.g. CI_ExtraClause_No, CI_ExtraClause_Yes. If you have many conditions and/or questions, this best practice will make them easy to decipher.

Clause Conditions Example

Example of Clause Conditions.

Making Clauses Conditional

The way you make your conditions functional in the template is by associating them with different parts of the Contract Document. This creates a situation where particular parts of the document are used only when certain conditions are true.

Example: CI-ExtraClause_Yes condition is applied when a contract author answers Yes to the question that asks if additional confidential information should be added, the additional clause will be pulled into the Main Agreement of the contract workspace. If the contract author answers No, then the clause will not be used.

Making Content Conditional

When you associate conditions with content, you can select multiple conditions and use the any of, all of, or none of options to use the conditions in different ways.

Conditions can also be set at the section level. If the conditions are not true, then the section and associated clauses will not be used. It’s important to apply the condition to the appropriate level. If we applied a condition to the clause instead the section, and the condition was not true, the resulting Main Agreement would contain a section without any clauses.

Note

SAP Ariba Best Practice: Name your conditions well so it’s intuitive what they are when viewing them in the outline view, as shown above. That way, you won’t have to go to the Conditions tab to remember what they do.

Testing Templates

To test conditions on a Main Agreement, you must use the Test Project Creation option. This option:

  • Allows template designers to test the experience of a user who is creating a workspace using the template.
  • Allows you to generate a Main Agreement from the end user point of view, so you can determine whether the clauses are dynamically changed as workspace values are changed

There are two different tools for testing templates:

  • Test Project Creation
  • Test Conditions

Only the Test Project Creation option allows template designers to test the conditions on clauses and sections. The initial screen shows the header information that users are asked to enter in the workspace creation wizard. When you test a template, fill in the values, answer any questions you want to test and click Create Test. The system will generate a test workspace and the associated Main Agreement and optional Contract Addendum. Open the document(s) and view the sections and clauses. You can open each document in either the outline view (as shown above) or select Open Draft to see the content as a Microsoft Word document. If you set up your conditions correctly, any conditionalized sections and clauses will be included if the conditions were true. They will be excluded if the conditions were not true.

The Test Conditions tool does not work for testing sections and clauses since you must open the document in order to see the results. The Test Conditions option only works for tasks, documents, and team members, which can be viewed using the workspace’s compact view, or by clicking the appropriate tab when the contract workspace is displayed in full view.

Create Conditions and Test Project Part 1

After completing this activity, you will be able to:

  • Create conditions on clauses in the Main Agreement
  • Create a Test Project to test clause conditions

Create Conditions and Test Project Part 2

After completing this activity, you will be able to:

  • Create conditions on clauses in the Main Agreement
  • Create a Test Project to test clause conditions

Log in to track your progress & complete quizzes