18.1 Release Notes - library.sciquest.comlibrary.sciquest.com/sites/default/files/release-notes/18.1 JAGGAER... · Packing Slip Number Added to Receipt Search Results ... approvers,

Last updated 4.8.2018. JAGGAER Confidential. © 2018, JAGGAER

18.1 PRODUCT RELEASE NOTES FOR ALL JAGGAER INDIRECT SOLUTIONS

APRIL 8, 2018 - FINAL VERSION

JAGGAER i www.JAGGAER.com

Table of Contents WELCOME ..................................................................................................................................... 1

OBJECTIVES ............................................................................................................................................ 1

18.1 SCHEDULING AND TRAINING OPPORTUNITIES ............................................................. 2

KEY DATES.............................................................................................................................................. 2

TRAINING OPPORTUNITIES .................................................................................................................. 2

THE FEATURE SNAPSHOT FOR 18.1......................................................................................... 4

SNAPSHOT KEY...................................................................................................................................... 4

FEATURE SNAPSHOT ............................................................................................................................ 5

GENERAL ENHANCEMENTS .................................................................................................... 11

JAGGAER Indirect and Solution Name Updates .............................................................. 11

Advanced Dynamic Workflow Rules Management Screen Enhancements ........................... 12

New Business Unit Search Feature in BU Management .................................................... 13

New Diversity Classifications Available .......................................................................... 14

Supplier Information Overlay Updates .......................................................................... 15

Form Request Template Versioning .............................................................................. 16

Projects Renamed to Work Groups ............................................................................... 17

Implementation of TLS 1.1 .......................................................................................... 18

EPROCUREMENT ...................................................................................................................... 20

SHOPPING AND ORDERING .............................................................................................................. 20

Updated User Interface and Navigation for Category, Commodity Code and UOM Mapping .. 20

Supplier-Related Rules Available for Requisition and Purchase Order Workflow .................. 21

Hosted Content Submission Updates ............................................................................ 23

Ability to Add a Non-Catalog Item on a Change Request ................................................. 24

Ability to Change a Line Item that was Generated from a Form ....................................... 25

New Notifications and Action Items Related to Change Requests ...................................... 26

External Communication Options for Change Requests ................................................... 27

Ability to Evaluate the Grand Total of a Change Request against the Grand Total of the Original PO

............................................................................................................................... 29

Ability to Evaluate a PO with Merged Changes to Determine if there is a Resulting PO Revision

............................................................................................................................... 30

PO and Requisition Document Configurations Evaluated for Matching Custom Fields for Change

Request Configuration ................................................................................................ 31

New Page for Managing Request Templates ................................................................... 32

JAGGAER ii www.JAGGAER.com

Ability to Evaluate Sets of Custom Fields in Form Request Workflow ................................. 33

CONTRACT COMPLIANCE TRACKING .............................................................................................. 35

Ability to Hide Inactive Contract Types ......................................................................... 35

Create Contract Wizard Updated .................................................................................. 35

ACCOUNTS PAYABLE ............................................................................................................... 37

Ability to Map Receipts to Invoices ............................................................................... 37

Ability to Trigger Export upon Receipt Submission .......................................................... 40

Receipts List Included in Invoice Export ........................................................................ 42

Ability to Create Receipts via Mobile App....................................................................... 42

Ability for Suppliers to Create an Invoice Via Email ........................................................ 43

Cycle Time Workflow Report Enhancements .................................................................. 46

Packing Slip Number Added to Receipt Search Results .................................................... 47

SUPPLIER MANAGEMENT ....................................................................................................... 49

Ability to Allow Suppliers to Sign Tax Documents via DocuSign ........................................ 49

Ability to Configure Registration Profile Custom Page Names to Multiple Languages ........... 52

Bank Routing Number Validation for US ACH and Wire Transfer Payment Methods in Supplier

Registration/Profile .................................................................................................... 53

Risk Management: Visual Compliance Enhancements ..................................................... 54

Supplier Search Defaults to Search In-Network Suppliers................................................ 56

Supplier Review Workflow - ERP Sync upon Approval ..................................................... 57

SOURCING ENHANCEMENTS .................................................................................................. 59


Sourcing Event Custom Fields ..................................................................................... 59

Make Item Quantity Field Supplier-Controlled ................................................................ 60

Enhanced Panel Questionnaire Analysis ........................................................................ 61

Stage-to-Stage Auto-Transfer of Panel Questionnaire Questions ...................................... 62

Event-Level Conditional Questions ............................................................................... 62

New Public Site Filters ................................................................................................ 63

CONTRACT LIFECYCLE MANAGEMENT .................................................................................. 65

Ability to Hide Inactive Contract Types ......................................................................... 65

Create Contract Wizard Updated .................................................................................. 65


New Contract Templates for Faster Contract Entry ......................................................... 67

New Contract Communication Center ........................................................................... 72

New Ability to Compare Documents.............................................................................. 76

JAGGAER iii www.JAGGAER.com

Word App Extended ................................................................................................... 79

Contract Request Template Versioning ......................................................................... 81

New Fields on Contract Export ..................................................................................... 82

SAVINGS MANAGEMENT ......................................................................................................... 84


JAGGAER 1 www.JAGGAER.com

Welcome

The 18.1 JAGGAER Product Release will be available in the production environment

starting April 8, 2018. The release includes features related to the following JAGGAER

Indirect solutions:

• eProcurement

• Accounts Payable

• Supplier Management

• Contract Lifecycle Management

• Sourcing

• Spend Analytics

• Savings Management

• Inventory Management

Objectives

The purpose of the Product Release Notes is to prepare administrators for the upcoming

release from a scheduling and application standpoint. There are two main goals of this

document.

• To provide a list of key dates associated with the upcoming release, including release

availability in both the test and production environment.

• To provide an overview of key features that are planned and committed for delivery

with the 18.1 release.

As a reminder, please refer to the Product Release Library at any time for updates and

additional information regarding the release:

http://library.sciquest.com

This document will help you:

• Prepare for JAGGAER Indirect version 18.1 – available in your production environment

on Sunday, April 8, 2018.

• Understand the impacts of new features on your end-users, approvers, administrators,

and other individuals using the system.

• Understand any changes required on your part to enable a feature of the system.

• Provide a starting point of “where to go” to learn more about the features and

functionality discussed in this document.


18.1 Scheduling and Training Opportunities

Key Dates

The table below provides a list of key dates for the JAGGAER 18.1 Product Release*.

Event

Date and

Time Description and Details

Release

Promotion:

Test Sites

Unavailable

Beginning

March 16,

2018, 8am ET

The 18.1 release will be promoted to the Test (usertest)

environment from Friday, March 16, 2018, 8am ET through Sunday,

March 18, 2018 12 pm ET. An email will be sent when the promotion

is complete.

Release

Validation in

Test

Environment

March 18, 2018

- April 6, 2018

(Three Weeks)

Three weeks prior to General Availability, release enhancements can

be viewed and tested in the Test environment. Draft documentation

is provided at this time (Release Notes, Online Searchable Help and

Handbooks).

Recommendation: It is recommended that clients perform

testing of functionality critical to your business as soon as possible

during this period - ideally during the first week. If any issues are

encountered, this will allow time for application adjustments and re-

testing.

Production

Unavailable

(Begin

Release

Upgrade)

Beginning April

6, 2018, 9pm

ET through

April 8, 2018,

12pm ET

The 18.1 release will be promoted to the Production environment

from Friday, April 6, 2018 9pm ET through Sunday, April 8, 2018

12pm ET. An email will be sent out when the promotion is complete.

Release

available on

Production

Sites

Sunday, April

8, 2018

This date indicates when the features and functionality associated

with 18.1 will be available on customer Production sites. Final

documentation provided at this time (Release Notes, Online

Searchable Help and Handbooks).

* Planned deviations to this schedule will be communicated to customers at least two weeks

in advance. JAGGAER is not liable for any system or data issues encountered during the

recommended period of system unavailability listed above (release promotion period).

Training Opportunities

To help prepare you for the 18.1 release, various educational videos are provided by

JAGGAER. Each of these opportunities is detailed below.


Video Name Description and Details

Preview Webinar (pre-

recorded video)

The pre-recorded video will present a preview of all features coming in

release 18.1. Available on the Product Release Library during the UIT

testing period.

Product Webinars (pre-

recorded videos)

Product-specific pre-recorded videos presenting a preview of features

coming in release 18.1. Available on the Product Release Library during the

UIT testing period.


The Feature Snapshot for 18.1

The product release provides features that directly impact requisitioners, approvers,

administrators, and other system users. These features are listed in summary form in the

Feature Snapshot below.

Snapshot Key

There are seven columns in the Feature Snapshot. Each of these is explained below:

• Feature Name –The feature title matches the heading found in the Preview Release

Notes (this document). For more information on the feature, locate the feature via the

table of contents. The features are listed in the order presented in the document.

• Related Products – The product or products associated with the enhancement. Use

this information to determine if the change impacts your organization. For example, if

the change is for AP Director, only those organizations using this product will be

affected by the change.

• Impacted Users– The user role or roles PRIMARILY affected by the enhancement. For

example, if a change is made to the way that a shopper selects a supplier, end user

would be listed in this column. For more details, such as level of impact (low, medium,

or high), please refer to the feature description.

• Integration Impact - Indicates if the feature may have impact on integration between

JAGGAER Indirect and other third-party systems used by your organization. Examples

would be changes to import or export files or features developed expressly for

integration. We recommend that administrators review all of these features to

determine if there is any integration impact.

• On by Default – Indicates that the feature is turned on (enabled) by default and no

configuration is required to take advantage of the new functionality.

• Requires Setup – Indicates that some type of setup or configuration is required. In

most cases, this is simply enabling one or more configuration options and enabling

permissions for the appropriate users.

• Contact JAGGAER– Indicates that someone at JAGGAER (Customer Support,

Customer Success Manager, or Sales) must be involved in order to enable and take

advantage of the feature. A new license may be required, workflow changes, etc.


Feature Snapshot

The following table provides a summary of features available starting April 8, 2018.

Feature Name Related Solutions Impacted

Users Integration

Impact On by

Default Requires

Setup Contact

JAGGAER

JAGGAER

Indirect and

Solution Name

Updates

All All None

Advanced

Dynamic

Workflow Rules

Management

Screen

Enhancements

All Admins None

New Business

Unit Search

Feature in BU

Management

All Admins None

New Diversity

Classifications

All JAGGAER Indirect

Solutions

(**Additional

configuration needed for

Supplier

Management, Sourcing,

Accounts Payable and

Contract Lifecycle

Management

Customers)

Admins,

End Users

None

Supplier

Information

Overlay Updates

All End Users None

Form Request

Template

Versioning

All Admins,

End Users

None

Projects

Renamed to

Work Groups

Contract Lifecycle

Management, Sourcing,

Savings Management

End Users None

Implementation

of TLS 1.1

All Admin



Users Integration

Impact On by

Default Requires

Setup Contact

JAGGAER

Updated User

Interface and

Navigation for

Category,

Commodity

Code and UOM

Mapping

eProcurement Admins None

Supplier-Related

Rules Available

for Requisition

and Purchase

Order Workflow


Hosted Content

Submission

Updates

eProcurement,

Inventory Management

Admins,

End Users

None

Ability to Add a

Non-Catalog

Item on a

Change Request

eProcurement Admins,

End Users

Low

Ability to

Change a Line

Item that was

Generated from

a Form


End Users

Low

New

Notifications and

Action Items

Related to

Change

Requests


End Users

Low

External

Communication

Options for

Change

Requests


End Users

Low

Ability to

Evaluate the

Grand Total of a


End Users

Low



Users Integration

Impact On by

Default Requires

Setup Contact

JAGGAER

Change Request

against the

Grand Total of

the Original PO

PO and

Requisition

Document

Configurations

Evaluated for

Matching

Custom Fields

for Change

Request

Configuration


End Users

None

New Page for

Managing

Request

Templates


End Users

None

Ability to

Evaluate Sets of

Custom Fields in

Form Request

Workflow


Ability to Map

Receipts to

Invoices

Accounts Payable Admins,

End Users

High

Ability to Trigger

Export Upon

Receipt

Submission


End Users

High

Receipts List

Included in

Invoice Export

Accounts Payable Admins High

Ability to Create

Receipts in

Mobile App


End Users

None

Ability for

Suppliers to

Create Invoice

Via Email

Accounts Payable Admins None



Users Integration

Impact On by

Default Requires

Setup Contact

JAGGAER

Cycle Time

Report

Enhancements

Accounts Payable End Users None

Packing Slip

Number Added

to Receipt

Search Results

Accounts Payable End Users None

Ability to

Configure

Registration

Profile Custom

Page Names to

Multiple

Languages

Supplier Management Admins None

Risk

Management

Enhancements:

Visual

Compliance

Workflow

Supplier Management Admins None

Ability to Allow

Suppliers to

Sign Documents

via DocuSign

Supplier Management Admins,

End Users

None

Bank Routing

Validation for US

ACH and Wire

Transfer

Payment

Methods


End Users

None

Supplier Search

Defaults to

Search In-

Network

Suppliers

Supplier Management

for Organizations also

using eProcurement

End Users None

Supplier Review

Workflow -

ERP Sync Upon

Approval


End Users

None

Sourcing Event

Custom Fields

Sourcing Admins,

End Users

None



Users Integration

Impact On by

Default Requires

Setup Contact

JAGGAER

Make Item

Quantity Field

Supplier-

Controlled

Sourcing End Users None

Enhanced Panel

Questionnaire

Analysis


Stage-to-Stage

Auto-Transfer of

Panel

Questionnaire

Questions


Event-Level

Conditional

Questions


New Public Site

Filters

Sourcing Admins,

End Users

None

Ability to Hide

Inactive

Contract Types

Contract Compliance

Tracking

(eProcurement),

Contract Lifecycle

Management

Admins,

End Users

None

Create Contract

Wizard Updated

Contract Compliance

Tracking

(eProcurement),

Contract Lifecycle

Management

Admins,

End Users

None

New Contract

Templates for

Faster Contract

Entry

Contract Lifecycle

Management

Admins,

End Users

Low

New Contract

Communication

Center

Contract Lifecycle

Management

Admins,

End Users

Low

New Ability to

Compare

Documents

Contract Lifecycle

Management

Admins,

End Users

None

Word App

Extended

Contract Lifecycle

Management

Admins,

End Users

None



Users Integration

Impact On by

Default Requires

Setup Contact

JAGGAER

Contract

Request

Template

Versioning

Contract Lifecycle

Management

Admins,

End Users

None

New Fields on

Contract Export

Contract Lifecycle

Management

Admins,

End Users

None


General Enhancements

The features listed in this section apply across all JAGGAER Indirect Solutions.

JAGGAER Indirect and Solution Name Updates

SelectSite is now JAGGAER Indirect, which is our suite of Source-to-Pay applications on a

single platform. The focus of JAGGAER Indirect is on solutions rather than simply on

products. In support of this, the following changes will be made to documentation in the

18.1 release:

• Anywhere that the documentation previously referred to SelectSite will be updated to

JAGGAER Indirect.

• JAGGAER has simplified the naming of the JAGGAER Indirect the solutions to reflect the

purpose of each solution. Documentation will be updated to refer to the solution names.

See the table below for additional information.

Solution Description

eProcurement

The JAGGAER Indirect eProcurement solution encompasses the following

Procure-to-Pay elements:

• Spend Management - Shopping, requisition management, order

management (previously referred to as Spend Director).

• Supplier Management - General supplier management functionality

that is bundled with the solution. If your organization uses Total

Supplier Manager, please see information below about simplified

naming for TSM.

• Contract Compliance Tracking - General contract management

functionality that is bundled with the solution. If your organization uses

Total Contract Manager, please see information below about simplified

naming for TCM.

Accounts

Payable Accounts Payable Director (and Accounts Payable Express) is now the JAGGAER

Indirect Accounts Payable solution.

Supplier

Management Total Supplier Manager is now the JAGGAER Indirect Supplier Management solution. Documentation and training will specify when a feature is applicable only to

this solution vs. general supplier management that comes bundled with other

solutions.

Contract

Lifecycle

Management

Total Contract Manager is now the JAGGAER Indirect Contract Lifecycle

Management solution. Documentation and training will specify when a feature is

applicable only to this solution vs. the Contract Compliance Tracking solution that is

bundled with eProcurement.


Solution Description

Sourcing Sourcing Director is now the JAGGAER Indirect Sourcing solution

Spend Analytics Spend Radar is now the JAGGAER Indirect Spend Analytics solution.

Savings

Management Portfolio Savings Manager is now the JAGGAER Indirect Savings

Management solution.

Inventory

Management Supplies Manager is now the JAGGAER Indirect Inventory Management solution.

Advanced Dynamic Workflow Rules Management Screen Enhancements

Advanced Dynamic Workflow (ADW) allows organizations to manage workflow rules in the

application. Workflow administrators can choose rule options and approvers for each ADW

step in workflow. In 18.1, we have made enhancements to the ADW Rules Management

screen. The available line-level and document-level workflow options are organized by data

type, making it easier for administrators to locate the appropriate option. In addition, Role

is now available as a search option when searching for users to be designated rule

approvers.

Impact

• Related Solutions: All JAGGAER Indirect Solutions

• End User Impact: None

• Admin User Impact: Low

• Integration Impact: None

Key Points of Feature

• This feature is ON by default.

• New Permissions related to this Feature: None

• In ADW, JAGGAER provides rule options that can be used as evaluation criteria on which

a workflow rule is built. Most of the options are related to one or more "data types". For

example, there are several rule options that evaluate user profile data, supplier profile

data, etc. Previously, the rule options were in a single, alphabetical list in a drop-down

field. As of 18.1, the rules are organized by the data type. Additional information:

• A new field has been added for both document-level and line-level rules. The Add a new

rule for a drop-down field lists the data types. When a data type is selected, the rule

options for that data type become available in the drop-down field to the right.


• There is an All option available that lists all rule options alphabetically.

• Some data types are available regardless of a user's licensed products (User Profile, for

example). Other data types are only available if the organization has related products.

Please see Configuring Advanced Dynamic Workflow in the online searchable help for

specific information about the data types and related rules.

• Part of creating ADW rules is selecting users to approve them. Approvers are selected

via user search. Search criteria includes name, position, status, etc. In 18.1, we have

added Role as field for user search. Additional information:

• When creating a rule, the user search feature displays when the Add Approver button is

clicked. The search window now contains a Role field. This is a drop-down field from

which the appropriate rule can be selected.

• Only Active roles are available.

• When a role is selected, only users associated with that role will display in the search

results.

• For additional information about ADW set up, please see Configuring Advanced Dynamic

Workflow in the online searchable help.

New Business Unit Search Feature in BU Management

Most organizations that use the Multiple Business Unit (MBU) feature have 20+ business

units. In Business Unit management, the BUs are listed in alphabetical order. Previously, a

user had to scroll through the list in order to locate the BU. In 18.1, we have added a

search feature, making it easier to locate the correct BU.

Impact






• This feature is ON by default for organizations that have licensed the MBU feature.


• A new search field is available on the Business Units tab in BU management. Take the

following steps to search for and manage a BU:

1. Navigate to Setup > Organization Structure and Settings > Add/Manage

Business Units.

2. Click on the Business Units tab.

3. The search field is located in the upper left corner above the list of BUs. Enter text in the

field.


4. Click Search. The list is filtered to only display BUs that match the search text.

• To help accommodate this change, the Create New Business Unit button that was

previously displayed below the list of business units has been removed. It has been

replaced by a Create New link located above the list. Click on the link to create a new

business unit.

• For additional information about managing business units, please see Business Unit

Management in the online searchable help.

New Diversity Classifications Available

JAGGAER continues to address customer needs related to tracking important diversity

information for suppliers by adding new classifications from time to time. With the 18.1

release, a new diversity classification for State of Ohio Encouraging Diversity, Growth

and Equity (OH-EDGE) is available under State Diversity Classifications. Customers

with Supplier Management, Sourcing, Accounts Payable, or Contract Lifecycle Management

must enable the new classification in order for it to be visible in the customer's supplier

portal. All other customers will see the new classification available by default for selection

on the supplier profile.

Impact

• Related Solutions: All JAGGAER Indirect Solutions (additional configurations needed in

Supplier Management, Sourcing, Accounts Payable, and Contract Lifecycle

Management)

• End User Impact: Low


• Integration Impact: Low

Key points of Feature

• This feature must be enabled for supplier use by customers with Supplier Management,

Sourcing, Accounts Payable, and Contract Lifecycle Management. It is ON by default for

all other customers.


• New State Diversity Classification for State of Ohio Encouraging Diversity,

Growth and Equity (OH-EDGE).

• Supplier Management, Sourcing, Accounts Payable, and Contract Lifecycle Management

customers can select the new diversity classification to be available to suppliers in the

Customer Branded Portal via Suppliers > Configuration Settings > Diversity

Configuration in the State Diversity Classifications section (assuming that

Diversity is configured to show in the Branded Portal under Registration Configuration).


• Suppliers will have the ability to select the new classification in their network supplier

profiles, but can select it for customer specific profiles only for those customers who

have made the new classification visible.

• A customer user with appropriate permissions may choose to enable the new

classification for the supplier in their view of the supplier profile.

• The new classification is listed on the Supplier Dashboard in the Supplier Diversity

Dashboard section. Customers can choose to hide the classification from display within

the application via field management.

• The new classification is available in the Diversity Classification search criteria in

advanced supplier search.

• The new classification can be included in the TSM Supplier Import/Export.

• For more information about diversity selections, see Diversity Classifications, and

Managing Diversity Selections in the Supplier Profile.

Supplier Information Overlay Updates

When a user selects a Supplier Name from a document, document search results, product

search, and other areas of the solution other than Supplier Search, an overlay displays with

the supplier's information. Previously, a Supplier page appeared with the basic, summary

information for the supplier as provided in the supplier's profile. The Supplier 360 page was

displayed as the last tab in the overlay. With the 18.1 release, the Supplier 360 tab is the

initial tab in the overlay. Also, the Supplier tab has been updated to a more organized,

readable format.

Impact



• Admin User Impact: None



• This feature is ON by default


• When selecting a Supplier Name from a document, document search results, product

search, and other areas (other than supplier search), an overlay displays the basic

supplier information:

• Supplier 360 is the initial tab displayed in the overlay (if enabled for the

organization).


• The Supplier tab provides the basic information from the supplier's profile

organized into areas of interest in the profile depending on the customer's licenses.

Form Request Template Versioning

Previously, there was not a way to create different versions of a Form Request template. A

finalized template could be copied, but this created an entirely new template. Versioning

provides the ability to update a template and to activate that update without having to

create a new one. It also allows organizations to seamlessly revert back to earlier versions.

In the 18.1 release, request template versioning is available.

Impact



• Admin User Impact: Medium





• To help accommodate this feature and other updates being made to Form Requests, a

new Manage Form Request Templates page has been added in the application. This

separates management of standard forms from the management of shopping-based

form requests (Procurement, Quick Quote, Check Request, Credit Memo, Generic). For

additional information about the new page, please see New Page for Managing Request

Templates. Note: The location of Supplier Request, Sourcing Event Request and Contract

Request template management has not changed.

• The initial creation of a form request is the "Draft" version (once it is saved). When a

new form request is Finalized, Version 1 is created. At this point, there is both a Draft

and Version 1 instance of the form request. Note: Upon 18.1 go-live all previously

finalized templates are automatically Version 1. Templates that were not finalized

remain in Draft status.

• Additional versions can be made from the Draft. As new versions are created, the

numbers increment (Version 2, Version 3, etc.). To create a new version:

1. Navigate to Administer > Shopping Settings > Manage Request

Templates. Locate the appropriate template.

2. Click on the Actions button and select Edit Draft. The Draft version of the template

displays. Make the appropriate updates.

3. Click on the Review and Finalize option on the left menu.


4. Click the Finalize and Activate button.

5. A Confirm pop-up window displays. Click Yes to finalize and activate the template.

• A new version is automatically made the active version when it's finalized. However, a

previous version can be made the active version. To reactivate a previous version:

1. Navigate to Administer > Shopping Settings > Manage Request

Templates. Locate the appropriate template.

2. Click on the Actions button and select View. The active version of template displays.

3. Click on the Choose Other Version link located on the top-right side of the screen.

4. Select the appropriate version.

5. Click on the Review and Finalize option on the left menu.

6. Click the Activate Template button.

• Any links to a form request template, such as favorites, dashboards or showcases, will

automatically be updated when a new version becomes the active version.

• Contract requests, Supplier Requests and Sourcing Event Requests will automatically

use a new active version. Important: If a new version is made active while a request

is in process, that request will continue on the previous active version. Only new

requests will use the new active version.

• Some organizations route documents through workflow based on responses to

questions on a template. When a revised template is made active, any workflow rules

associated with a question response will remain valid, provided the question is not

deleted and the response is not deleted or changed. If the question is deleted or a

response is deleted or changed as part of the revision, workflow will need to be edited.

If it is not edited, documents will no loger be routed based on the response.

• For additional information about creating form requests, please see Form Request Setup

and Configuration in the online searchable help.

Projects Renamed to Work Groups

With the 18.1 release, the term "Projects" has been replaced with the term "Work Groups"

throughout JAGGAER Indirect. This change accompanies the introduction of the new Project

Based Procurement solution, where the term “Projects” is used differently.

Work groups are used in Contract Lifecycle Management, Sourcing, and Savings

Management to organize and control access to an organization's records.

Organizations that have renamed "Projects" to another name are not affected by this

change, and the option is available to use the field thesaurus to return the name back to

"Projects.”

IMPACT

• Related Solutions: Contract Lifecycle Management, Sourcing, Savings Management


• End User Impact: Medium



KEY POINTS OF FEATURE

• This feature is On by default.

• New Permissions related to this Feature: None.

• "Projects" have been renamed to "Work Groups" on all systems that are using the

default field name "Projects". Organizations that have renamed "Projects" to another

name are not affected by the change.

• To change the term "work groups" to another name, navigate to Setup > Field

Management > Configure Field Thesaurus. Expand the Work Group listing under

the list of available terms to view all variations of the "work groups" term. For each

variation, select the Override checkbox in the appropriate language, and enter the

display name you wish to use. Click Save.

Implementation of TLS 1.1

Use of TLS 1.1 or later is required in the JAGGAER Indirect UIT and Production

environments. This change affects all connections to JAGGAER Indirect solutions, including

integrations and SSO.

JAGGAER SUPPORTS THE FOLLOWING TLS CIPHERS:

• TLS 1.2 Cipher List

• AES256-GCMSHA384

• AES256-SHA

• AES256-SHA256

• ECDHE-RSA-AES256-CBC-SHA

• ECDHE-RSA-AES256-GCM-SHA384

• ECDHE-RSA-AES256-SHA384

• AES128-GCMSHA256

• AES128-SHA

• AES128-SHA256

• DHE-DSS-AES128-GCM-SHA256

• DHE-DSS-AES128-SHA

• DHE-DSS-AES128-SHA256

• ECDH-ECDSAAES128-GCM-SHA256

• ECDH-ECDSAAES128-SHA

• ECDH-ECDSAAES128-SHA256


• ECDH-RSA-AES128-GCM-SHA256

• ECDH-RSA-AES128-SHA

• ECDH-RSA-AES128-SHA256

• ECDHE-ECDSAAES128-GCM-SHA256

• ECDHE-ECDSAAES128-SHA

• ECDHE-ECDSAAES128-SHA256


• ECDHE-RSA-AES128-GCM-SHA256

• ECDHE-RSA-AES128-SHA256

• TLS 1.1 Cipher List

• AES256-SHA


• AES128-SHA

• DHE-DSS-AES128-SHA

• ECDH-ECDSAAES128-SHA

• ECDH-RSA-AES128-SHA


eProcurement

This section details enhancements to the eProcurement solutions that are available in the

18.1 release.

Shopping and Ordering

The following shopping and ordering features will be added and/or updated.

Updated User Interface and Navigation for Category, Commodity Code and UOM Mapping

In 18.1, we have made changes to the screens used for managing category, commodity

code and UOM mapping. Changes will include:

• The user interface has been updated from tab-based navigation to a menu-driven

navigation.

• Commodity code mapping import/export and category mapping import/export,

currently managed from different screens, is managed on a single screen.

• The navigation path for accessing the screens has been updated.

• Users can view the history of changes and updates made to the mappings.

IMPORTANT: The new and updated functionality requires JAGGAER to migrate system data

to a new back-end process. It is very important that organizations test business processes

that use the mappings to ensure they are working as expected.

Impact

• Related Solutions: eProcurement







• The navigation path for accessing mapping configuration has been changed. It is now

accessed by navigating to Setup > Hosted Catalog and Ordering Configuration >

Category, Commodity and UOM Mapping Sets. This replaces the previous navigation

path for accessing mapping.


• The layout of the mapping user interface has been changed from tab-based navigation

to menu-driver navigation. The main areas for mapping now display in a menu on the

left. Clicking on a menu item opens the corresponding configuration screens on the

right. Note: In a future release, the concept of multiple mapping sets will be introduced.

Mapping sets will display in the menu, with the mapping areas displayed as sub-items.

When this functionality goes live, any existing mappings will be designated as the

"default" mapping. In 18.1 the Default Mapping menu item is already included and

mapping areas are sub-items.

• Previously, category mapping import/export and commodity code mapping

import/export were configured on separate screens. These can now be done from the

same screen. A single Import/Export screen is available.

• You have the ability to hide the menu (giving you more space on the screen). Click the

Hide Mapping Sets button to hide the menu. To display the menu once it's hidden,

click the Show Mapping Sets button.

Supplier-Related Rules Available for Requisition and Purchase Order Workflow

In 18.1, new, supplier-related rules are available for workflow. The objective of adding

these rules is to allow organizations to evaluate and route PRs and POs for a specific

supplier, based on the information in the supplier's profile. These rules evaluate data such

as questionnaire responses, diversity and insurance information, legal structure, commodity

code values and NAICS code values.

Note: The rules are available in standard workflow, which is managed by JAGGAER, and

Advanced Dynamic Workflow (ADW), which is managed by an organization's workflow

administrator.

Impact






• This feature is ON by default for organizations that use ADW but requires setup.

Organizations that use standard workflow must contact JAGGAER to include one or more

of these rules.


• The supplier-related rules allow organizations to evaluate PR and PO documents based

on information in the supplier profile.

• The following rules are now available in PR and PO Workflow:


• Country of Origin - Evaluates the value in the Country of Origin field in the supplier

profile. It is available as a line-level rule for PR workflow and as a document-level rule for

PO workflow.

• Custom Questions - Evaluates a custom question identified in the Supplier Registration

document. It is available as a line-level rule for PR workflow and as a document-level rule

for PO workflow.

• Diversity Classification - Evaluates diversity classifications in the Supplier Registration

document. It is available as a line-level rule for PR workflow and as a document-level rule

for PO workflow.

• Is Diversity Certification Expired - Evaluates if a supplier's diversity classification is

expired. It is available as a line-level rule for PR workflow and as a document-level rule

for PO workflow.

• Is Insurance Certification Expired - Evaluates if a supplier's insurance certification is

expired. It is available as a line-level rule for PR workflow and as a document-level rule

for PO workflow.

• Legal Structure - Evaluates the supplier's Legal Structure as identified in the Supplier

Registration document. It is available as a line-level rule for PR workflow and as a

document-level rule for PO workflow.

• Questionnaire Category - Looks for the presence of absence of specific Questionnaire

Categories in a Supplier profile. It is available as a line-level rule for PR workflow and as a


• Questionnaire Questions - Evaluates the Questionnaire Question identified in the

Supplier Questionnaire. It is available as a line-level rule for PR workflow and as a


• Questionnaire Response Status - Looks for the presence or absence of specific

Questionnaire Response Statuses in a Supplier profile. It is available as a line-level rule

for PR workflow and as a document-level rule for PO workflow.

• Questionnaire Titles and Supplier Response Status - Looks for the presence of a

specific response status for a question based on the question title. It is available as a line-

level rule for PR workflow and as a document-level rule for PO workflow.

• Set of NAICS Code Values - Looks for the presence or absence of a specific set of

NAICS code values in a supplier registration. Also can be used to look for an empty NAICS

code (no value). Rule can also be configured to evaluate Primary only, Secondary only, or

both Primary and Secondary NAICS. It is available as a line-level rule for PR workflow and

as a document-level rule for PO workflow.

• Set of Supplier Commodity Code Values - Looks for the presence or absence of a

specific set of supplier commodity code values in a document. Also can be used to look for

an empty commodity code (no value). It is available as a line-level rule for PR workflow

and as a document-level rule for PO workflow.

• Single NAICS Code Value - Looks for the presence or absence of a specific NAICS code

value in a supplier registration. Rule can be configured to evaluate Primary only,

Secondary only, or both Primary and Secondary NAICS. It is available as a line-level rule

for PR workflow and as a document-level rule for PO workflow.


• Single Supplier Commodity Code Value - Looks for the presence or absence of a

specific supplier commodity code value in a document. It is available as a line-level rule

for PR and PO workflow.

• For additional information about Advanced Dynamic Workflow, please see Configuring

Advanced Dynamic Workflow in the online searchable help.

Hosted Content Submission Updates

Customers who manage a catalog internally, such as for a stockroom, have previously been

required to submit content and pricing for the catalog via a text, tab-delimited (.txt) file.

Large files must be zipped prior to submission. Also, content and pricing extracts have only

been available in .txt format. With the 18.1 release, customers managing their own

catalogs now have the ability to submit an Excel file for content and price updates, as well

as request content and price extracts in Excel format. When submitting large files, there is

no need to zip the Excel formatted file. This makes the loading process much more efficient.

The text file format will continue to be supported, and is required for special submissions

such as images and Chemical structures.

Also with the 18.1 release, the existing Brand attribute for hosted catalog items is now

searchable when customers use a keyword search in Product Search. Also, a new attribute

for UDI Code is available. It is a text attribute that is not searchable. Any Unique Device

Identification code as per FDA guidelines can be entered in this attribute.

The Categories and Attributes spreadsheet has been updated to indicate that Brand is

now a searchable attribute and that UDI Code is an available text attribute.

Impact

• Related Solutions: eProcurement, Inventory Management





• This feature is ON by default but is optional for use


• Customers managing their own catalogs can now submit content and pricing in Excel

format. The following submission types will accept the Excel format:

• Content Update/Add

• Content Replace All/Discontinue

• Content - Replace all/delete

• Content - Discontinue

• Content - Delete


• Content - Reactivate

• Price jobs Updated/Add, Replace All, Change Part numbers

• When a file is submitted in Excel format, the corresponding validation, warning and

error files are also in Excel format.

• There is no need to zip large Excel files. Large files can be submitted in Excel format as

is. You must continue to zip large .txt files.

• The following submission types must continue to be submitted in .txt format:

• Misc - Images

• Misc - Change Part Numbers

• Misc - Chemical Structures

• The Request Extracts page (Contracts > Hosted Catalog Items and Price > Request

Hosted Content and Price Extracts) has a new option for File Type.

• The default value is Excel.

• You can select Tab Delimited to generate the extract in the .txt format.

• If the number of rows being extracted exceeds 1 million, the export will

automatically generate in .txt format, regardless of the File Type selection made.

• The Brand attribute for hosted catalog content is now a searchable value when

customers use a keyword term in Product Search.

• A new UDI Code attribute is available for suppliers to enter a Unique Device

Identification code as per FDA guidelines.

Ability to Add a Non-Catalog Item on a Change Request

JAGGAER continues to enhance the Change Request feature by providing additional

capabilities for making changes to the original PO. As of 18.1, the feature has been updated

to allow non-catalog items be added on a change request. Users can add one or more non-

catalog line items per supplier.

Impact






• This feature is ON by default but requires setup.



• The functionality is automatically available to organizations that have the Change

Request feature enabled. It does not require any set up in the change request document

configuration.

• A user must have the View/Use Non-Catalog Item permission. (Permission

Settings > Shopping, Carts & Requisitions > Shopping) to add a non-catalog item

on the change request.

• To add a non-catalog item on a change request:

1. Access the change request. In the Lines section of the Summary screen, locate the

supplier for which you are adding the item.

2. Click the Add non-catalog item for this supplier... link. The Add Non-Catalog

Item overlay displays.

3. Enter the information for the non-catalog item.

4. Click Save and Close to save the item and return to the change request. Click Save

and Add Another to save the item and add another non-catalog item.

• Once the change request has gone through the approval process the non-catalog line

item is merged on the PO document.

• Items added on a PO may have an effect when the PO export is merged with other

third-party systems. Please work with your system administrator or JAGGAER customer

support to ensure that there are no integration issues.

• For additional information about creating a change request, please see Creating a

Change Request in the Shopping Handbook or the online searchable help.

Ability to Change a Line Item that was Generated from a Form

JAGGAER continues to enhance the Change Request feature by providing additional

capabilities for making changes to the original PO. As of 18.1, the feature has been updated

to allow line items that were generated from a form to be updated. Users will be able to

make changes to both quantity and price.

Impact









• This feature is automatically available for organizations that have the change request

configured to allow line item changes. This can be enabled by going to Setup >

Configure Documents > Configure Change Request and selecting the Line item

only fields checkbox.

• Changes can be made to price or quantity for line items that originated from a form

purchase.

• Items changed on a PO may have an effect when the PO export is merged with other

third-party systems. Please work with your system administrator or JAGGAER customer

support to ensure that there are no integration issues.

• For additional information about creating a change request, please see Creating a

Change Request in the online searchable help or the Shopping Handbook.

New Notifications and Action Items Related to Change Requests

In 18.1, new notifications and action items related to change requests are available.

Notifications communicate when change requests have been created, assigned, rejected,

completed or are pending in workflow. Notifications can be enabled for individual users or

on the role level. They can be sent as emails, in-application notifications or both. Action

items notify users when a change request has been assigned or lands in a workflow step for

which a user is the approver.

Impact








• New notifications are listed below. There are additional notifications related to the new

feature that allows you to assign a change request to another user. Please see Ability to

Assign a Draft Change Request for additional information.

• Change Request submitted into Workflow - Notifies the owner (Prepared For user)

when a change request enters workflow.

• Prepared By - Change Request Assigned Notice - Notifies PO "Prepared By" users

when a change request has been assigned.

• Prepared By - Change Request rejected/returned - Notifies the PO "Prepared By"

user when a related change request been rejected or returned.


• Prepared By - Receive PR and PO notifications for Change Requests Assigned

to Me - Notifies the "Prepared By" user on the change request when the related PR and

related PO are being processed through workflow.

• Change Request pending approval in Workflow - Notifies a user when a change

request enters a workflow folder/workflow step for which that user is an approver.

• Change Request Workflow Notification available - Notifies approvers on a

notification step in change request workflow that there are new workflow notifications.

Workflow notifications are informational only; an approver does not reject or approve a

requisition from a notification.

• Change Request Workflow complete / Merged to PO - Generated when the

change request completes the Create PO step of Requisition workflow. This means that

the change request was approved and the changes were merged to the original PO. The

purchase order will now go back through PO workflow with the new changes.

• Change Request rejected/returned - Notifies the owner of the change request when

an approver has either rejected the change request. Note: This notification is also

triggered if an assigned draft has been returned to the creator. Please see Ability to

Assign a Draft Change Request for additional information.

• Notifications can be enabled for an individual user in the user profile or for multiple

users assigned to a role via role setup. A new Change Requests group is available in

Notification Preferences. The new notifications are listed in this group.

• The new notifications can be sent be sent as emails, in-application notifications, or both.

• System emails are managed by accessing Administration > Email Management

> System Emails. A new Change Requests group is available. The new notifications

are listed in this group.

• The notification preferences have been added to the XML and Advanced CSV user

export. If your organization utilizes the user export to integrate with other

internal systems, this may affect the integration. Please work with your system

administrator and/or JAGGAER to ensure there are no issues.

• Separate action items are now available for change request actions. The action items are

listed under Change Request in the Action Items list.

External Communication Options for Change Requests

In 18.1, there are two new external communication options available for change requests.

The Resend to Suppliers on Change Request flag indicates if the purchase order will be

resent to the supplier when a change request is created. The Resend to ERP System

Connections on Change Request flag indicates if the purchase order will be resent to an

ERP system when a change request is created. When this flag is enabled, the user can

select the appropriate ERP.

The options are configurable on the organization level through change request document

setup and can be overwritten on the actual change request document.


Impact








• Configuration fields have been added that determine if a purchase order related to a

change request should be resent to a supplier and/or an ERP.

• The default settings for the fields is set in change request configuration (Setup >

Document Configuration > Change Request Configuration).

• Change request documents inherit the settings from the configuration but they can be

overwritten. The Summary screen contains the fields. They are located in the External

Communications section on the screen.

• Information about the settings:

• Resend to Suppliers on Change Request - When this field is set to true, the PO will

be resent to the supplier. A flag is set when the change is merged to the PO. When the PO

goes through the export step, the step will abide by the flag and resend the PO to the

supplier.

• Resend to ERP System Connections on Change Request - When this field is set to

true, the PO will be resent to an ERP. A flag is set when the change is merged to the PO.

When the PO goes through the export step, the step will abide by the flag and resend the

PO to the ERP that you select. ERP options are displayed below the field. The user can

select the appropriate ERP(s) to which the PO should be resent. Important: Resending

the PO to an ERP may have an effect on the integration. Please work with your system

administrator or JAGGAER support to ensure that activating this setting will not cause any

issues.

• To enable the resends, each field must be set to true. Upon 18.1 go live, both fields will

be set to false.

• For additional information about Change Request Configuration, please see Configuring

Change Request Options in the online searchable help.

• For additional information about creating change requests, including overwriting these

settings, please see Creating a Change Request in the online searchable help or the

Shopping Handbook.


Ability to Evaluate the Grand Total of a Change Request against the Grand Total of the Original PO

In some cases, an organization may want to evaluate the delta between an original PO

grand total and the grand total of the PO after a change request. For example, it's possible

that if a grand total exceeds a certain dollar amount, the document may need to be routed

to a specific user for approval. In 18.1, we have provided a new document-level workflow

option that evaluates the grand total of the original PO against the grand total of the PO

with change request changes.



administrator.

Impact






• This feature is ON by default but requires setup for organizations that use ADW.

Organizations that use standard workflow need to contact JAGGAER to have the rule

enabled.


• A new document-level workflow option has been added to Requisition, Purchase Order,

Invoice and Fulfillment workflow. The new Change Request Total Difference rule

evaluates the total monetary difference between the change request and the original PO.

• When configuring the rule, a user selects an operator (equal to, not equal to, etc.)

enters a monetary value.

• If an organization uses multiple currencies, the user can also select a currency for the

rule. The Currency field defaults to the user's default currency.

• Organizations that use ADW can set up the new rule in an existing workflow step. If a

new workflow step is required, please contact JAGGAER. Organizations that use standard

workflow must contact JAGGAER to have the rule set up in existing workflow step and to

add a new workflow step.


Ability to Evaluate a PO with Merged Changes to Determine if there is a Resulting PO Revision

Organizations that use Banner Finance (or another ERP system that uses an asynchronous

message process) may need to route a PO through workflow based on whether or not a

revision was made to the document due to a merged change request. Exports to some ERP

systems should not occur until after the merged changes are finalized. In 18.1, we have

provided new document-level rule options in PO Workflow. These options can evaluate the

following:

• Does the PO have a merged change request that created a revision?

• Does the PO have a merged change request but no revision was created?

These workflow objects can be used in a workflow step that evaluates if a PO has a revision

from a change request. This allows organizations to configure whether to export the

document before or after the Revise PO step. For example, the Banner Finance PO Update

message normally occurs before the Revise PO step. However, when there is a merged

change request that has not yet been finalized, workflow configuration needs to exclude the

document from the first Banner PO update step. A workflow step will then need to be added

to have a second Banner PO update message sent after the Revise PO step with the

condition that the PO has a revision from a merged change. This workflow step will need to

be added by JAGGAER.

Note: Once the workflow step has been added, organizations that use Advanced Dynamic

Workflow can add the rules in ADW configuration. Organizations that use standard workflow

will need JAGGAER to add the rules.

Impact






• This feature is ON by default but a workflow step needs to be added in order to use the

new workflow options.


• The following workflow rule options are now available in Purchase Order workflow:

• Has Merged Changes without Revision - This rule evaluates if a PO has merged

changes from a change request that are not yet finalized in a revision. It can be set to

true or false.

• Has Revision with Merged Changes - This rule evaluates if a PO has a revision

resulting from a change request.


• If your organization is already using the change request feature and this step is added,

it will be important to ensure that the integration with Banner or other ERP system is not

affected.

• For additional information about ADW configuration, please see Configuring Advanced

Dynamic Workflow in the online searchable help.

PO and Requisition Document Configurations Evaluated for Matching Custom Fields for Change Request Configuration

Organizations have the ability to allow splittable and grouped custom fields to be updated

on a change request. However, it is possible for the PO document configuration and the

Requisition document configuration to contain different custom fields. This can cause issues

if a change is made. Currently, the application does not check the document configurations

for matching custom fields. In 18.1, the document configurations are evaluated. If an

organization is newly enabling the option to edit splittable or grouped custom fields, and the

custom fields do not match, the system will not let it be enabled. If an organization enabled

the functionality prior to 18.1, a user will be able to create a draft but will not be able to

edit the custom fields.

Impact








• In order to successfully pass changes to splittable or grouped custom fields between

requisitions and purchase orders, it's imperative that the document configurations for

both document types contain the same custom fields. In this release, JAGGAER has

added a behind-the-scenes process that compares the configurations. If the custom

fields do not match, one or both of the following occurs:

• If an organization enabled the functionality that allows custom fields to be changed prior

to 18.1, any user who creates a change request will see a message that the grouped and

splittable custom fields cannot be edited because POs and requisitions do not have the

same set of fields. This will occur until the document configurations have been updated to

match.

• An organization that attempts to newly enable the functionality will not be able to do so. If

an administrator attempts to turn on the Splittable or grouped custom fields setting in


change request configuration, a message that the functionality cannot be enabled

because POs and requisitions do not have the same set of fields. A list of the fields for

each document type will display.

• For information about document configuration, please see Document Setup and

Configuration in the online searchable help.

New Page for Managing Request Templates

Forms and Form Requests are useful tools within the application. Forms are laid out similar

to paper-based forms and can be used to order goods and services. Requests can also be

used to order goods and services, but can be used for several other purposes as well.

Requests are filled out in a wizard-type interface.

Previously, Forms and Request templates were administered and managed from the same

page in the application. In 18.1, have added a new page for managing Request templates,

thereby separating Forms and Requests. This is being done to help accommodate updates

that are being made to the Requests and to make a clear distinction between what is a

Form and what is a Request.

Note: This new page is for the management of shopping and ordering-based form request

templates; Procurement, Quick Quote, Credit Memo, Check Request and Generic. Navigation

to other form request template management, such as Contract Requests, Supplier Requests

and Sourcing Event Requests, has not changed.

Impact

• Related Solutions: All







• Previously, Form templates and Request templates were created and managed from the

same page. This page was accessed by navigating to Administer > Shopping

Settings > Manage Form/Form Request Templates. As of 18.1, the following

navigation changes have been made:

• To access Form administration, navigate to Administer > Shopping Settings >

Manage Forms.

• To access Requests administration, navigate to Administer > Shopping Settings

> Manage Request Templates.


• Upon 18.1 go-live, existing forms and request templates are automatically located on

the appropriate page.

• The new page is applicable only to form requests previously managed in the same area

as forms. These include Procurement, Credit Memo, Check Request, Quick Quote

Request and Generic request templates. Other templates (Sourcing Event, Contract

Request, and Supplier Request) are still managed from their respective areas in the

application

• The Manage Forms page has not changed. Forms are still listed and accessed as they

were previously. The only exception is that the Build New Form Request button is no

longer available. Requests must be built from the new page.

• The Manage Request Templates page has a different layout from the previous page.

Templates are presented in a list format in order to provide more information about the

template on the page.

• The list of templates by entering text in the Title/Description field. The text will be

matched to text in the Request title or description and only matching Requests are

displayed. The list can also be filtered by form purpose by selecting an option in the Form

Request Purpose drop-down field.

• New Requests can be created by clicking on the Build a New Form Request button

located in the top-right corner.

• To import a Request template, click the on the Build a New Form Request button

and select Import a Form Request Template.

• Existing templates are listed and the list includes the following information: Title, Active

Version, Version Description, Status (Draft or Finalized), Created Date and Last

Updated Date. Note: Request template versioning is a new feature being introduced in

18.1. Please see Form Request Template Versioning for information.

• Similar to other lists in the application, a user can configure the number of list items per

page using the Per Page dropdown field. A user can also browse through the pages

using the .

• Each template in the list has a corresponding Actions button. The available actions

depend on the status of the template. Draft templates can be viewed and edited. Finalized

templates can be viewed, copied, archived. You can also view the draft of the finalized

template.

Ability to Evaluate Sets of Custom Fields in Form Request Workflow

While Procurement form requests go through standard requisition workflow, all other form

requests go through a separate "Form Request" workflow. This includes both Check Request

and Credit Memo requests. Both of these types of requests may include custom fields. In

18.1, additional rule options are available in Form Request workflow to evaluate sets of

custom field values on Check Request and Credit Memo request documents.



administrator.


Impact

• Related Solutions: eProcurement, Accounts Payable







• The following workflow rule options are now available in Form Request workflow:

• Set of Custom Field Values - This rule looks for the presence or absence of a specific

set of custom field values in the document. Also can be used to look for an empty custom

field (no value).

• Spend Total Against a Set of Custom Field Values - This rule evaluates the total

amount charged against a group of custom field values.

• At this time, Credit Memo Requests and Check Requests are the only form requests that

can have custom fields included. If one or both of the custom field rules are included,

they will not be triggered if a different type of form request goes through Form Request

workflow (Quick Quote, Generic, etc.).

• For additional information about workflow setup, please see Workflow Management in the

online searchable help.


Contract Compliance Tracking

This section details enhancements that are available in the 18.1 release related to Contract

Compliance Tracking.

Ability to Hide Inactive Contract Types

A new toggle link on contract types provides the ability to hide or show inactive contract types.

Impact

• Related Solutions: Contract Compliance Tracking







• A Show Inactive/Hide Inactive toggle link is displayed in the top right corner of the

Contract Types column on the Contract Types page.

• Clicking Show Inactive displays inactive contract types in gray and italicized font. This is

the default setting.

• Clicking Hide Inactive hides inactive contracts.

• An inactive parent contract type is displayed if any of its child contract types are active.

Create Contract Wizard Updated

The Create Contract wizard has been streamlined from a multi-step contract creation wizard to a

single step.

Impact

• Related Solutions: Contract Compliance Tracking








• The Create Contract wizard has been streamlined from a multi-step contract creation wizard to

a single-step:

• Users enter a contract name and a contract type on the initial entry screen.

• Once a contract type is chosen, the Currency field is displayed if the use of multiple

currencies is enabled.

• When the Create Contract button is clicked, the contract is created and opens to the

contract Header page.

• The Start Date and End Date fields are no longer in the wizard. Once a contract is created,

they are displayed on the contract Header page and users can enter dates.


Accounts Payable

The following Accounts Payable features are being added or updated with 18.1:

Ability to Map Receipts to Invoices

Most manufacturing industry procurement orders are large quantities of raw material that are

fulfilled and received over an extended period of time. While a vendor may submit an invoice for

the entire quantity to the customer, processes require businesses to pay the vendor as goods are

received. Customers need the ability to map receipts to invoices as those receipts are generated.

With the 18.1 release, customers will have the ability to map receipts to invoices as goods and

services are received (Receipt Mapping for Invoices, or RMI). This action can be done manually if

the supplier and other settings are configured appropriately. Also, a workflow object is available to

allow the mapping to occur automatically based on a mapped custom field.

Once a new configuration is enabled, customers can associate a supplier class to the appropriate

suppliers, include a new RMI field on requisition and purchase order documents, use search tools to

find RMI documents, and request to add workflow configurations to route documents with the RMI

flag.

Impact

• Related Solutions: eProcurement with Accounts Payable



• Integration Impact: High


• This feature is OFF by default and you must contact JAGGAER to enable

• A new AP Configuration option (Accounts Payable > AP Administration > Configure

AP Settings) is available to Enable Receipt Mapping for Invoices. Once enabled, users can

select a Custom Field for Receipt Mapping for the automatic mapping of receipts to

invoices. The available custom fields in the list meet these criteria:

• Does not allow splits

• Has placement in custom field configuration

• Is on the Default active Invoice Doc Config - line level only

• May or may not have values in custom field configuration

• A new supplier class for Receipt Based Invoices Enabled can be associated to suppliers

with whom you have an agreement to map receipts to invoices as those goods are received.

This will label suppliers as RMI enabled. JAGGAER must make the new class available to the

organization, then the organization can make it active, associate a search preference,

associate an icon, etc. If the supplier has this class associated and is added to the cart, the


Receipt Based Invoices field on the document configuration will be enabled by default for those

suppliers.

• A new system field called Receipt Based Invoices is must be enabled for requisition and

purchase order document configuration. This flag will show as ON for suppliers that have

the supplier class Receipt Based Invoices Enabled. The flag can also be manually checked

or unchecked on the PR and on a draft PO. The field is:

• A checkbox element

• On the requisition document - Supplier level field only

• On the PO document - Header only (summary page setting)

• Impact of changes to AP Configuration Setting or Supplier Class in Requisition and PO:

• When a Requisition has any line flagged as RBI and the AP configuration setting is turned

off or the supplier class is inactivated, the draft cart cannot be submitted and an error

message will display.

• Once a Requisition is submitted, any changes to the setting or the supplier class do not

impact the submitted requisition.

• The PO is not impacted by the Receipt Based Invoice setting being on or off for the

supplier. The values are inherited from the Requisition at the time the Requisition was

submitted into workflow.

• A new Status Flag search option for With Receipt Based Invoice is available on Advanced

search for requisitions and purchase orders. When selected, search results will include

documents with the RMI flag.

• Advanced Dynamic Workflow (ADW) rules available to :

• Evaluate RMI supplier class, and/or the RMI flag on the document.

• Evaluate the discrepancy between the mapped receipt line total and total invoice. The

workflow step will evaluate the discrepancy and return the absolute value of the

difference.

• The action of reopening and adding new Receipt Based Invoice PO's to the receipt will

trigger the auto-mapping logic.

• A workflow robot is available to notify the Requisition Owner with the discrepancy information.

• A new notification for Receipt Mapping Discrepancy Notification is available in the

user profile (Profile > Notification Preferences > Accounts Payable). When enabled and the

workflow robot is triggered, the Requisition owner will be notified.

• The new system email for Receipt Mapping Discrepancy Notification (Administer >

Email Management > System Emails: Accounts Payable) is sent to the Requisition owner

when the notification preference is enabled.

• When this feature is enabled, a new tab displays on the Invoice document for Receipts

that allows for manual mapping of receipts to invoices, and allows the user to manage and

view all receipts mapped (automatic or manually) to the invoice. The tab displays the number

of associated receipts in parenthesis. This tab will show only for invoices that associated PO's

with one or more Receipt Mapped Invoice PO lines.

• The Receipts section indicates receipts associated to the invoice. Select the Receipt No.

hyperlink to navigate to the receipt. If no receipts have yet been associated, a message

displays.

• The Invoice Line Summary section provides the line information from the Invoice.

Information includes the Invoice Line Number, Product Name, PO Line Number, the


Invoice Line Quantity/Cost, Invoice Line Total, Mapped Receipt Line Total, Discrepancy

message (highlighted), and Receive Status. The Add Receipt hyperlink is available for

each line to associate on a line by line basis (if manually adding receipts).

• You can select the Print Preview icon to see a preview of the Receipts tab with links for

the PO number(s) and the Receipt number(s).

• The Receipts tab does not display on a Draft Invoice. It will only display on a Finalized

invoice in workflow with at least one PO associated with the invoice has RMI flagged lines.

• Requisitions and PO's flagged with Receipt Based Invoices can only contain accounting code

Splits by Percent of price and Percent of quantity; the document cannot contain any

splits by amount.

• Auto mapping of Receipts to an invoice:

• You must contact JAGGAER to update your Invoice Workflow to include the Automapping

Workflow Robot in your configuration.

• When a Receipt is created for a PO that has at least one line flagged as RBI and has a

value for the Custom Field for Receipt Mapping, that PO will automatically be mapped

to an Invoice associated with the same PO and that has the custom field on the invoice

document. For example, if you have chosen a custom field called "Bill of Lading" as the

Custom Field for Receipt Mapping and you add a Receipt and put a value in for the Bill

of Lading, that Receipt will be automatically mapped to the Invoice associated with the

PO.

• Manually add a Receipt to an invoice: (This assumes Receipts have been created for a PO,

but the custom field value was not present or mapping is not configured):

• On the Receipts tab for the invoice, select the Add Receipt link for the appropriate

Invoice Line to be received. Enter or search for a receipt in the Add Receipt box.

• Once one or more Receipt No. are selected, click Add Selected to close the overlay. The

Receipt No.(s) is then populated in the Add Receipt box. Click Save to associate the

Receipt to the Invoice.

• The Receipt and associated line(s) are reflected on the Invoice tab. Select the Receipt

hyperlink to navigate to the receipt. Select to expand the line information to see the

Receipt associated with the line. Select the Remove hyperlink to remove the receipt line.

• You cannot map a Receipt to more than one Invoice.

• When an invoice is created from a mix of RMI and Non-RMI PO's, the Receipts tab only

displays the PO's that are RMI and the Receipt lines that are associated to the RMI PO.

• A new Receipt Based Invoice column is now included in the PR and PO Document Search

Result Full Export. The value is indicated as TRUE if the line was flagged as RBI and FALSE if

it was not.

• Receipt Based Invoice is a new system field available for the creation of Requisition and

Purchase Order Custom Export Templates (Documents > Document Search > Create and

Manage Export Templates).

• In some cases, receipts mapped to an invoice can be reopened:

• If the receipt has all Non-RMI lines:

• The receipt cannot be reopened once it is exported. A message displays indicating

that the receipt cannot be reopened because it has been exported to an external

system.


• The receipt cannot be reopened if it is not exported but the PO has an invoice that

has completed workflow. This is no change from current functionality of Non-RMI Po

based receipts.

• If the receipt has all RMI PO's associated:

• The Reopen action is always available, regardless of the receipt export status.

• The Reopen action is always available when the receipt has a PO that has an invoice

that has completed workflow.

• If the receipt has a mix of RMI and Non-RMI PO's AND none of the invoices have

completed workflow:

• The Reopen action is available when the receipt has not been exported.

• The Reopen action is not available when the receipt has been exported, and a

message displays indicating the Receipt cannot be reopened because it has PO lines

from a non-Receipt Based Invoice type.

• If the receipt has a mix of RMI and Non-RMI PO's and at least one of the invoices has

completed workflow:

• The Reopen action is not available. A message is displayed indicating the Receipt

cannot be reopened by the invoice has completed workflow and has lines from a non-

Receipt Based Invoice Type.

• The Receipt does not keep a snapshot of the PO RBI flag status after it is created and

completed. If the PO RBI status changes, the refresh on the receipt will pick up the latest

changes and the re open will become available or not based on the PO RBI flag status at

the time.

• This feature does not apply to Credit Memo's.

Ability to Trigger Export upon Receipt Submission

Most manufacturing industry procurement orders are large quantities of raw material that are

fulfilled and received over an extended period of time. Standard procurement processes use

receipts to encumber funds so when a receipt is completed, an export to the ERP is needed so that

funds are earmarked. With the 18.1 release, connection settings support Receipt export. The

receipt export includes accounting codes derived from the PO, and can be configured with a trigger

and schedule. The details for the export queue and completion are captured in the receipt history

log.

Impact








• You must contact JAGGAER to enable an updated Receipt Export DTD version 1.3 which

exports the receipt in the new format with custom codes.

• Receipts are now supported via Connection Management (Setup > General Site Settings >

Document Export Settings > document export > connection mgt):

• Select New Connection or edit an existing connection.

• Enable the Supports Receipts option to see complete additional configurations (similar

to other export configuration options):

• Supports Receipt exports from document search: If enabled and you choose Export

from the Receipt Search Results drop down, the selected Receipts will be included in

export to ERP.

• Include attachments in export

• Documents per message

• Once exported, the document (receipt) will show the exported details in History.

• You can create a schedule for the Receipt Export (Setup > General Site Settings > Document

Export Settings > document export > scheduling mgt):

• When you select to create a New Schedule, there is now a new Doc Type selection for

Receipts; when selected only the receipt Connections are displayed for selection.

• Select the Internal and other schedule parameters.

• You can create a trigger for the Receipt Export (Setup > General Site Settings > Document

Export Settings > document export > trigger mgt)

• When you select to create a New Trigger, a new Document Type is available for Receipts,

and the following additional selections display.

• Event - On Receipt Complete.

• Action - Select Export on every status change.

• Export to - select from available receipt export schedules.

• A new email notification for Receipt Export failure notification (User Profile > Notification

Preferences > Administration & Integration) is available. This notification will be sent to users

who have it enabled when the receipt export fails.

• The email content is managed via Field Management under Org Receipt Export

XML delivery error (Setup > Field Management > Manage Field Names and Help Text >

General > misc > Email Notification).

• The notification message can be managed via Field Management at Setup > Field

Management > Manage Field Names and Help Text > Administration > Notification

Manager > Receipt Export Failure Notification.

• Receipt Export has been added to the list of options under Administer > Find and Fix

Errors. From this page, the list of Receipt Export errors can be seen and requeued

• There is no change to the requirements for having the ability to reopen a receipt. Current

functionality does not allow a receipt to be reopened once it is exported, or if the PO has an

invoice that has completed workflow. However, If the receipt has any Receipt Based Invoicing

lines, the ability to resend is based on different criteria. See Ability to Map Receipts to Invoices

for details.


Receipts List Included in Invoice Export

With the 18.1 release, several features have been added to allow for the mapping of receipts to

invoices. This is especially beneficial to organizations who place large orders and receive them

incrementally over time. The Invoice Export process previously did not contain receipt information.

In order to fully support the receipt mapping feature, the invoice export has been updated to

include the list of receipts associated to an invoice from a Receipt Based Invoice PO.

Impact






• This feature is ON by default if you have Invoice Export Version 2.0 enabled. Contact JAGGAER

if you are unsure of your current version or would like to enable Version 2.0.

• Invoice Export Version 2.0 DTD has been updated to allow the list of receipts associated via

mapping to an invoice to be included. You must contact JAGGAER to enable the DTD.

• The export will only show receipts that are mapped to the invoice. If the associated PO has a

receipt created but it is not mapped to the invoice, it will not be included in the export:

• ReceiptLineStatus shows the status of the receipt line: Received, Returned or Cancelled.

• ReceiptLineTotal will not show negative numbers if the line was returned or cancelled.

Ability to Create Receipts via Mobile App

Many manufacturing industry procurement orders are large quantities of raw material that are

fulfilled and received over an extended period of time. The processes require businesses to map

the invoices to receipts as generated or received. In addition, many manufacturing and industrial

businesses have receiving staff that use mobile devices to generate and submit receipts as

products are delivered to the facility.

With the 18.1 release, customers utilizing the JAGGAER Mobile App now have the ability to create a

receipt from a purchase order number. When a new Mobile configuration option is enabled, the

Mobile App includes a menu navigation for "Receipts" for users who have the permission to create

receipts. Users have the ability to create a quantity or cost based receipt from a Purchase Order.

Impact







• This feature is OFF by default but can be enabled by an administrator

• A new setting is available under Setup > General Site Settings > Manage Mobile

Configuration > Mobile Options:

• Users may create receipts via mobile - When this setting is enabled, users with

permission to create receipts will see a new menu navigation in the Mobile App for

Receipts.

• In the Mobile App, a new menu page for Receipts contains two options: Create Quantity

Receipt and Create Cost Receipt.

• When either option is selected, you must enter a PO Number and click Select PO.

• If multiple PO's have the same number, the user will see a list of all available PO's

matching that number along with the creation date. The user can choose the

appropriate PO and proceed.

• The page refreshes with the PO Number and Supplier Name as Read Only. The user can

modify/enter a Receipt Name, Receipt Date, Packing Slip No., and enter the quantity or

cost for each item, indicating if it is being Received or Returned.

• The delete option is available for all lines. However, if the receipt has only one line,

the delete is not allowed since a receipt must have at least one line.

• Click Complete when done, and a confirmation message displays that a Receipt was

created for the PO.

• Completed receipts are available in the desktop application in a submitted status and

associated to the PO. The Receipts tab on the invoice also displays receipts created through

mobile and has them available for mapping.

• Draft receipts created in the Mobile App are not available in the desktop application. Only

completed receipts are available.

Ability for Suppliers to Create an Invoice Via Email

Suppliers can send invoices to customers electronically, via the Customer Branded Portal, fax or

mail. Currently, when a supplier sees that a Purchase Order has been created from a customer,

they must trigger the generation of an invoice through a system or manual process. With the 18.1

release, customers now have the ability to allow a supplier to create an invoice without having to

separately log into the portal or use another process. For PO-based Invoices, customers can choose

to send an email from the purchase order to the supplier's primary remittance contact or can use a

new workflow process that will automatically send an email to the supplier when the PO is

distributed. The new system email contains a link that allows the supplier to complete the details

needed to submit the invoice to the customer. For Non-PO Invoices, the customer will configure an

email that includes a new placeholder that suppliers will use to fill in the line information in order to

submit the invoice.


Impact






• This feature is OFF by default and can be configured by an administrator.

• New settings are available in the Supplier Profile > About > System Settings:

AP Configuration section:

• Enable PO based Email Invoices: If enabled, you can manually send or use a workflow

process to send a system email from a distributed Purchase Order in order for the supplier

to complete and submit an invoice from the email link.

• Enable Non-PO based Email Invoices: If enabled, you can manually send an email

from the supplier's profile that allows the remittance contact to create and submit a non-

PO invoice from the email link.

• A new workflow robot is available that will automatically send an email to the primary

remittance contact listed in the supplier profile once the PO is distributed. Contact JAGGAER to

include this step in your workflow process.

• A new invoice source for EMail will be shown in search results and as a new search filter. The

invoice source can also be used in workflow processes.

• New System Emails are available: Administer > Email Management > System Emails,

under the Accounts Payable list:

• PO based Email Invoice Notification - This email is sent to the supplier Primary

Remittance Contact when the customer selects to send the email from the purchase order,

or when a workflow process is invoked (if configured).

• PO based Email Invoice Confirmation - This email is automatically sent to the supplier

user who creates and submits a PO-based invoice from an email.

• Non-PO based Email Invoice Confirmation - This email is automatically sent to the

supplier user who creates and submits a non-PO invoice from an email.

• The email for Non-PO based invoice creation can be configured at the point you send the email

to the supplier from the supplier profile. Or, you can configure a template under Supplier

Email Templates (Suppliers > Communication > Email Templates) . The content of the email

must include the new placeholder Non-PO Invoice Creation Link.

• The organization system setting to Exclude URL links in Document-based Emails must be

OFF for the placeholder to appear in the email to the supplier (Setup > General Site Settings

> System Settings and Configuration : Email Setting section).

• Using the PO based Invoice From Email feature:

• The supplier setting for Enable PO based Email Invoices must be checked.

• The supplier must have a primary remittance contact.


• Contact JAGGAER to update your workflow process to include the step that will

automatically send an invoice to the primary remittance contact once the PO is

distributed.

• To manually send an email to a supplier for a PO Invoice: From Document Actions on a

Purchase order, select Send Create Invoice Email to the Supplier. The system email

(noted above) will be sent to the supplier's primary remittance contact as listed in the

supplier profile. A confirmation message will display that the email was sent.

• If there is no primary remittance contact email address, an error message displays and

the email will not be sent.

• Using the Non-PO based Invoice From Email feature:

• The supplier setting for Enable Non-PO based Email Invoices must be checked.

• The supplier must have a primary remittance contact.

• Optional but recommended: Configure a new Email Template for suppliers to create non-

PO based invoices from the email:

• Go to Suppliers > Communication > Email Templates and select to create a new

template.

• Configure the template information as appropriate for your organization.

• The content of the email must include placeholder Non-PO Invoice Creation Link.

See Managing Supplier Email Templates in the Supplier Management section of the

online searchable help for additional information about creating templates.

• From the Available Actions in Supplier Search, or from Supplier Actions on the Supplier

Profile, select Send Email to Supplier:

• For Select Contact Types, select Remittance.

• Note: If you select a different contact type, the supplier validation for the email

address will fail when they attempt to create the invoice from the link.

• Enter the Email information as appropriate.

• If you have configured an Email Template, select the configured template. You can

make edits to the template if appropriate for this particular supplier. You must include

the placeholder Non-PO Invoice Creation Link.

• If you have not configured an email template, enter a Subject and content as

appropriate. You must include the placeholder Non-PO Invoice Creation Link.

• You can also request that JAGGAER provide your organization with a URL to include in emails

sent to a supplier outside of the application that will enable the supplier to create a Non-

PO Invoice by selecting the link. This is a different function than sending the email from within

the application from the supplier's profile with a configured email.

• When the supplier user receives the email and selects the link:

• PO Based Invoices:

• The supplier clicks the button for "Click here to submit an Invoice for the referred

PO". The Purchase Order Number is listed in the submitted line of the email by

default.

• The Invoice Date, Invoice Owner, and Remit To address is displayed and is read-only.

The Supplier can modify the Due Date and enter a Supplier Invoice No. The Supplier

Invoice No. is not required.


• The PO lines are listed with amounts, and the supplier can modify the quantity, delete

a line, and add Discount, tax, shipping & handling charges.

• The supplier must click the reCAPTCHA checkbox before clicking Submit.

• A confirmation page displays that an invoice has been created along with the Invoice

Number.

• The supplier user will receive a confirmation email that the invoice was created.

• If the supplier attempts to click the link again, the supplier can continuing invoicing

until the PO is fully invoiced. When it is fully invoiced, a message will display that the

PO is fully or over-invoiced along with the invoice numbers already created.

• If the supplier has access to a portal, they can view the invoice in the portal.

• Non-PO Based Invoices:

• The supplier clicks the button for "Non-PO Invoice Creation Link".

• The supplier must enter their email for validation purposes. This must be the

primary remittance contact email as listed in the supplier's profile, regardless of

who the email was sent to.

• The supplier must click the reCAPTCHA checkbox before clicking Validate.

• The page refreshes with the Invoice Date and Remit To address displayed as read-

only. The Supplier can modify the Due Date and must enter a Supplier Invoice No.

The Supplier Invoice No. is not required.

• The Lines section contains entry boxes for Product Description, Unit Price and

Quantity, and must click Add Non-PO Item to add the line.

• When finished entering items, the supplier must click the reCAPTCHA checkbox before

clicking Submit.

• A confirmation page displays that an invoice has been created along with the Invoice

Number.

• The supplier user will receive a confirmation email that the invoice was created.

• If the supplier has access to a portal, they can view the invoice in the portal.

• The link in the email does not expire and can be used repeatedly.

Cycle Time Workflow Report Enhancements

Invoice Cycle Time reports analyze the time it takes for an invoice to go through workflow. These

reports are useful in helping organizations to determine areas for process improvements by

identifying where delays are happening in the workflow process. Two reports, Invoice Create to

Invoice Export and Invoice Submit to Invoice Export, are available from the Accounts Payable

or Reporting menus.

A Cycle Time - Invoice Workflow report was made available in January 2018. This report

provides the information in the current reports, as well as additional details about each workflow

step for the invoice. Also, a new Cycle Time - Export page was made available at that time to

access export requests generated from the new Invoice Workflow report.

Previously when applying filters for the Cycle Time - Invoice Workflow report, all Business Units

for the organization (if configured) were displayed regardless of the user's access permissions.


With the 18.1 release, the Business Unit selections display based on the user's profile (User Roles

and Access > Access > Business Unit Assignments: Document Search settings).

Note: The Cycle Time - Invoice Workflow report includes invoices beginning July 28, 2017.

Data for invoices prior to that date are available in the Invoice Create to Invoice Export and

Invoice Submit to Invoice Export reports.

Impact








• The Cycle Time - Invoice Workflow report (Accounts Payable > Reports) has been

updated to include only those Business Units applicable to the user:

• When generating the report, select More Options link to see all report filters.

• In the Business Unit dropdown, only those Business Units accessible to the user display.

Previously all organization Business Units displayed.

• The following must be in place for the Business Unit filter to display only accessible values:

• Organization is configured to Restrict Access by Business Unit (Setup > Organization

Structure and Settings > Add/Manage Business Units > General Settings)

• User DOES NOT have permission to View or Edit Organization Orders (Permission Settings

> Orders > My Orders/Organization Orders) or to View Organization Invoices (Permission

Settings > Accounts Payable > Accounts Payable)

• User is restricted to Business Units in the user profile (User Roles and Access > Access >

Business Unit Assignments: Document Search settings).

• For example, if the organization has 10 active business units and the user issuing the report

has access to two of those business units, only the two business units (along with All and No

Business Unit selections) will display. If All is selected, all the business units to which the user

has access will be applied to the results.

Packing Slip Number Added to Receipt Search Results

Many organizations record a Packing Slip Number when receiving goods. Previously, the Packing

Slip Number was shown on the Receipt view but not in Receipt Search Results. With this release,

the Packing Slip No is a new column in Receipt Search Results.


Impact

• Related Solutions: Accounts Payable






• Packing Slip No is a new column shown in Receipt Search Results.

• Packing Slip No. on the Receipt Document and the new Packing Slip No in document search

results are two different fields, managed separately via Field Management. If you modify the

name of the field or visibility for the Packing Slip No. field on the Receipt Document, the

change is not reflected for the Packing Slip No in Document Search Results. You must make

changes to both fields, if appropriate.


Supplier Management

This section focuses on updates to the JAGGAER Indirect Supplier Management solution. Features

in this section do NOT apply to general supplier management that is bundled with other solutions.

Please note that additional features explained in other sections of this document also impact

Supplier Management, including:

• The Manage Supplier Request Templates page (Suppliers > Configuration Settings)

has been updated as a result of the Form Request enhancements in this release. Please see

Form Request Template Versioning in the General Enhancements section for more information.

Also, see Supplier Requests in the JAGGAER Indirect Supplier Management Handbook or

online searchable help for more information on this functionality.

• A new diversity classification is available for suppliers. Please see New Diversity

Classifications Available in the General Enhancements section for additional information.

• The supplier information overlay available from documents, document search results and

product search has been updated to be better organized and more readable. Please see

Supplier Information Overlay Updates in the General Enhancements section.

• Updates to the Manage Commodity Codes page (Suppliers > Configuration Settings

> Commodity Codes), including the ability to search the commodity code list by code or

description. See Updated User Interface and Navigation for Category, Commodity Code

and UOM Mapping in the eProcurement Enhancements section for more information on that

feature. Also, see Commodity Codes in the JAGGAER Indirect Supplier Management

Handbook or online searchable help for additional information on this functionality.

Ability to Allow Suppliers to Sign Tax Documents via DocuSign

Many customer organizations require suppliers to submit signed tax documents in the supplier

profile. Previously, a supplier might be required to submit a scanned image of a signed document

because there was no ability to electronically sign the document from within the system. With the

18.1 release, customers can now enable an option to allow tax documents to be signed via

DocuSign. A new registration configuration is available for customers to Enable DocuSign in the

Tax Information section of Registration Configuration. The organization must have

eSignature Settings configured with a valid DocuSign connection.

The option is available for all tax types. If the supplier signs a document via DocuSign, the

customer will have the ability to accept or decline DocuSign changes. This feature applies to tax

information provided via the Customer Branded Supplier Profile, the customer's view of the supplier

profile, as well as the customer's proxy view of the profile.

Users can continue to manually upload signed documents. A new Tax Type level configuration

setting for e-Signature Required will allow customers to require e-Signature certification for

manually uploaded documents.

Also with this feature, the Tax Information page in the customer's view of the supplier profile has

been updated to display more of the tax document information upon landing on the page. The tax


information records are listed in table format, including the Tax Type, year, if documentation is

attached, and if the document has been verified via e-Signature or signed via DocuSign.

Impact

• Related Solutions: Supplier Management





• This feature is OFF by default but can be configured by an administrator.


• New Registration Configuration Options: Suppliers > Configuration Settings >

Registration Configuration > Entity Registration or Individual Registration

• A new option is available when configuring the Tax Information section:

• Select Tax Information > Section Configuration

• The new Enable DocuSign option is off by default. When enabled, the ability to sign

a tax document via DocuSign will appear for all tax types available in the registration

configuration.

• Your organization must have a valid DocuSign connection configured under Suppliers

> Configuration Settings > Registration Configuration > eSignature

Settings). The supplier user is not required to have a DocuSign account in order to

sign the document via DocuSign. See eSignature Documents in Supplier Registration

for instructions on setting up the eSignature connection for DocuSign.

• When configuring specific Tax Types (W-9, W-8BEN, etc.) for the Tax Information

section, a new option for e-Signature Required is available for each type:

• The setting is off by default.

• When enabled, the user manually uploading the associated tax type document will be

required to certify the document. Previously the certification for manually uploaded

documents was optional.

• When DocuSign is enabled:

• When adding tax information in the supplier profile or a supplier registration, a Sign

Document button will display. When selected, the document to be signed will open with

information pre-populated. Users can edit and add information as needed, sign the

document, and save it to the system.

• Before the DocuSign process can begin, the user will be prompted to save the Tax

Document record with the Tax Document Name and Year information.

• Users continue to have the ability to manually upload the tax document instead (no

change to previous functionality).

• The DocuSign action is logged in the supplier profile History for the tax record.


• The Tax page in the customer view of the Supplier Profile has been updated. Navigate to the

Supplier Profile and expand the Legal and Compliance section. Select the Tax page.

• Previously, the tax documents were listed on the left and the user had to select one to see

additional details. Now the Tax Information displays in table form with the following

information:

• Tax Document Name - The name given to the Tax Document when it was added.

This can be edited. Click the name to view and/or edit information for the document.

• Tax Type - The type of tax document. Once added, this information cannot be

edited.

• Tax Document Year - The Year for the Tax Document, if provided.

• Tax Documentation - If a file is attached to the record, it is listed here.

• e-Signature - You can allow suppliers to certify the tax information via an e-

signature process or sign document via DocuSign. The appropriate indication is given

here. A red x indicates the tax document has not been certified or signed via

DocuSign. A green check indicates the document has either been certified via e-

Signature or has been signed via DocuSign.

• Signature Status - Indicates if the document has been signed via e-Signature,

DocuSign, or not signed.

• To create a new tax record, click the Add Tax Information button and choose the

appropriate Tax Type from the dropdown selections. Only those tax types enabled in your

organization's Registration Settings will display. An overlay will display to complete the

Tax Document Name, Year, and other document options.

• Completing the Tax Document Name and Year is unchanged from previous

functionality.

• Depending on the organization configuration for DocuSign and e-Signature

requirements, the following options may display:

• Sign Document - If the organization has enabled DocuSign, click the Sign

Document button. A confirmation will display asking you to save the tax record.

Click Yes to continue. The DocuSign window will then open and direct you to

complete the signature process on behalf of the supplier. When the signing

process is complete, you will be directed back to the overlay, and the Signature

Status will indicate DocuSigned and you can click Save Changes to save the tax

record.

• Editing a DocuSigned document - select from the Actions dropdown

button next to the Signed Document text to Download, Sign a New

Document, or Delete the signed document. The Signature Status will update

accordingly.

• Manually upload the document instead - Select this option to manually

upload a document. The Select file button will display. Click on the file to be

attached or drag and drop the file into the gray area next to Select file. You

may choose to give the document a different name than the actual file name by

simply editing the value once it has been associated. This does not change the

underlying document name itself. You can also choose to Download a Pre-

populated Tax Document. When manually adding a file, you may also be

prompted to select I certify this tax document and follow the instructions to

complete the e-Signature process.


• Editing a manually uploaded document - You can remove the

attachment by selecting the x button, or replace it with another file.

• The supplier user will see the changes for the e-Signature requirement and DocuSign

options as per the organization's configurations in the Customer Branded Portal.

Ability to Configure Registration Profile Custom Page Names to Multiple Languages

Supplier Management customers have the ability to add custom profile fields and custom sections

in the Supplier Registration configuration. The customer can choose to translate profile fields and

associated Instructional Text into multiple languages. Previously, customers did not have the ability

to configure custom profile section names into multiple languages. With the 18.1 release, a new

Edit Translations button is available when configuring a custom profile section name in supplier

registration (Suppliers > Configuration Settings > Registration Configuration: Entity

Registration or Individual Registration). When selected, the user can choose which languages

should be supported for the field, and enter the appropriate text for each. The ability to translate

the section name is also added to the Manage Translations page under Registration

Configuration. The custom profile section translations can also be imported and exported from

the Manage Translations page, allowing for changes in bulk rather than field-by-field.

Impact








• When configuring a custom profile section in Entity Registration or Individual

Registration, (Suppliers > Configuration Settings > Registration Configuration) an

Edit Translations button is available for the Section Name to enter the appropriate text for

selected languages.

• When a language is selected, a text box displays for you to enter the appropriate

translation and save your changes. If you select a Language, you must enter a value for

the field.

• Updates to the translations are captured in Configuration Settings > History.

• Supplier and customer users viewing the supplier profile / registration will see the custom

profile section name displayed in their selected language with the appropriate translation,

if configured. If there are no translations for the field, the user will see the custom profile

section name displayed in the customer organization's default language.


• Edits can also be made to the Customer Profile Section names from the Manage Translations

page (Suppliers > Configuration Settings > Registration Configuration). Custom

sections are displayed if there is at least one custom profile field included in the section.

• Expand the section to see the section name. Click the Edit button to select other language

translation options for the section name. Changes are captured in History for the

corresponding registration type.

• When you select to Export from the Actions dropdown, a new Custom Section Name

option is available and is selected by default. When selected, the export will include a

spreadsheet for Custom Section Name fields and translations.

• When you select to Import from the Actions dropdown, selecting Custom Section

Name will now also import the Custom Section Name fields and translations.

• Translations will display to customer users in the supplier profile view, as well as the Supplier

Registration (Proxy) view.

• Translations will display to suppliers in the Customer Branded Portal.

• See Manage Translations for Instructional Text and Custom Profile Registration in the

JAGGAER Indirect Supplier Management Handbook or online searchable help for

additional information.

Bank Routing Number Validation for US ACH and Wire Transfer Payment Methods in Supplier Registration/Profile

For customers with the Onboarding license, the Supplier Profile includes Payment Method

information that can be entered by the customer or supplier user. Previously, the Routing

/ Transit Number for ACH and Wire Transfer payment methods with a Canada or United States

bank address was validated against the required Routing or Transit Number format for the country,

but the actual value was not validated. With the 18.1 release, the Routing / Transit Number

value for United States bank addresses for ACH and Wire Transfer methods is validated as per the

Federal Reserve Services (frbservices.org) database.

If a valid Routing / Transit Number is entered, the bank name displays underneath the field.

Otherwise, an error message displays. Users cannot save the payment method if the provided

value is not valid for the country.

This validation occurs for customer users who add or edit ACH or Wire Transfer payment

methods for a supplier in the Supplier Profile (Accounts Payable section) or via the Proxy

Registration (Payment Information page) view. The validation also occurs for supplier users in

their Network Portal as well as Customer Branded Portals.

Impact









• When completing supplier profile / registration information for the ACH or Wire Transfer

payment method with a Bank Address country of United States, the Routing / Transit

Number value will now be validated as existing for an actual institution.

• Values are validated as per Federal Reserve Services information (frbservices.org).

Information from Federal Reserve Services is refreshed daily.

• This validation also applies to wire transfer payment information provided in the Supplier

XML Import:

• The import process will validate Routing / Transit Number numbers for US and Canada

for new ACH and Wire payment types.

• The import process will NOT validate the Routing / Transit Number for existing

payment information; however, an error message will display for invalid numbers in the

UI.

• Upon go-live, if an invalid number exists for United States bank addresses, the user will see an

error message displaying below the routing number field. You must enter a valid routing

number in order to edit or save the payment method.

• Customer users will see this change reflected in the Supplier Profile, as well as when viewing

the supplier's registration in Proxy view.

• Suppliers will see this change reflected in the Network Portal, as well as in each Customer

Branded Portal.

Risk Management: Visual Compliance Enhancements

With the 17.3 release, customers were given the ability to enter existing Visual Compliance account

credentials in the application, and run Visual Compliance Checks on a supplier in order to identify

and authenticate suppliers. With the 18.1 release, customers utilizing Visual Compliance will now

see additional information about the Visual Compliance check results on the Legal and

Compliance > OFAC / Restricted Party Check page in the supplier's profile. Also, the Visual

Compliance can be included in Advanced Dynamic Workflow configurations so that the check is

automatically run and the supplier/document is routed based on the Alert type result.

The advanced supplier search has been updated to include the ability to search by Visual

Compliance Max Alert Type and Visual Compliance Last Updated Date. These two new criteria are

also available as filters in supplier search results.

Impact







• The additional Visual Compliance status details ON by default. The Visual Compliance Workflow

configuration is OFF by default and you must contact JAGGAER to enable.


• The Visual Compliance Check results have been updated to display additional Alert information.

The page is located under the Legal and Compliance section of the Supplier Profile (Suppliers

> Manage Suppliers > Search for Supplier > Legal and Compliance > OFAC /

Restricted Party Check). Note: The Visual Compliance options only displays on the OFAC /

Restricted Party Check page when you have configured your existing credentials in the

application.

• When you select to run a Visual Compliance Check, the following information is now

displayed:

• Maximum Alert Type Found - This is the highest level of alert found for the supplier,

based on the search criteria:

• Green - no match found

• Yellow - Matched on Individual Name or Company Name

• Red - Matched on Individual Name, Company Name or both

• Double Red - Matched on Individual Name, Company Name or Location

• Triple Red - Matched on Individual Name, Company Name, Location or Country

• Time of Last Query - The last time and date the Visual Compliance Check was run for

the supplier.

• Search Criteria - Click to expand the details for what was used to search for the supplier.

• Message and details about Alert Type, if found - If an Alert Type other than Green is

found, additional details display including the List and Notes associated with the alert

record.

• Visual Compliance Workflow Routing: While you can navigate to the supplier's profile to

run the Visual Compliance Check at any time, you can also choose to configure your

organization's workflow processes to run the Visual Compliance check and be routed based on

the result Alert type. Contact JAGGAER if you would like to include the Visual Compliance

check for any of the following workflow processes:

• Supplier Registration

• Supplier Review

• Requisitions (line level)

• Purchase Orders (document level)

• Invoices (document level)

• Sourcing Pre- and Post-Bid

• The workflow process will include a robot that will automatically run the Visual Compliance

Check for the supplier when the document / supplier enters the step. The check is performed

using the following parameters:

• Individual Name or Company Name

• Locations in this order: Physical, Remittance, Fulfillment

• Country


• When a Visual Compliance Check is run (via the UI or workflow), the action and result is

captured on in the History for the supplier's profile.

• A new document level ADW workflow element for Visual Compliance Alert Type is available.

You can select to create the rule for one of the following values or not one of the

following values:

• Error Running Check

• Not Run

• Green

• Yellow

• Single Red

• Double Red

• Triple Red

• In Supplier Advanced Search (Suppliers > Manager Suppliers > Search for a

Supplier), two new criteria are available in the Compliance section:

• Visual Compliance Max Alert Type - Begin typing or click the search icon to see and

select from a list of all possible values. Search results will display for suppliers with the

selected Alert Type(s) and meeting other search criteria.

• Visual Compliance Last Updated Date - Select the appropriate date value or range

from the dropdown to see suppliers that had a Visual Compliance check within that time

frame and meeting other search criteria.

• When Supplier search results display, two new filter sections are listed on the right for

Visual Compliance Max Alert Type and Visual Compliance Last Updated Date. Values

can be selected or deselected to further filter the results list.

• The Visual Compliance details can be included in the Supplier Excel Export. From Supplier

Search Results, select an export action from the Available Actions dropdown.

• Visual Compliance information is contained in the Supplier General Profile information.

• Visual Compliance Maximum Alert Type Found and Visual Compliance Time of

Last Query are two new columns in the Supplier General Profile tab of the Supplier Excel

Export.

Supplier Search Defaults to Search In-Network Suppliers

When eProcurement customers search for suppliers, the search engine defaults to searching across

all suppliers available to the organization. Supplier Management customers, however, would rather

see in-network suppliers in a supplier search. With the 18.1 release, organizations with Supplier

Management and eProcurement solutions will now see their supplier search Relationship filter

default to In-Network suppliers. The user can change to see Out of Network or All suppliers if

appropriate.

Impact

• Related Solutions: Supplier Management for Organizations also using eProcurement








• With the 18.1 Release, the supplier search for Supplier Management customers using

eProcurement will default to search In-Network Relationship status.

• Select Advanced search to expand the search criteria, and change the Relationship

value to All or Out of Network.

Supplier Review Workflow - ERP Sync upon Approval

Currently, if any changes are made to a supplier profile and the supplier enters Supplier Review

workflow, changes are constantly synced to the ERP system. This raises concerns that supplier data

may be changed by multiple users and exported to the ERP system without being verified by the

appropriate departments. To ensure only approved and valid information is exported to ERP

systems, with the 18.1 release customers can enable a process that will automatically enter the

supplier into the Supplier Review Workflow process when a configured field is changed in the

supplier's profile. This process will "pause" the ERP export until the supplier is approved in supplier

review workflow. Changes made in the UI will only be synced to the ERP once the changes are

approved via Supplier Review Workflow. Changes made via supplier xml import will continue to be

immediate, since those changes are coming from the ERP system.

When this feature is enabled, administrators will have access to a new page Configure Internal

Review Fields. This page lists all fields available to be synced to the ERP system. The

administrator will select the fields that should trigger the ERP approval when changed.

You must contact JAGGAER to implement this feature. Some changes may be required to your

Supplier Review Workflow process.

Impact








• Organizations that sync to an ERP system can request to update Supplier Review Workflow so

that when changes are made to configured supplier profile fields, the supplier ERP Sync

process is paused and no data will be synced until the change is approved.


• When this feature is enabled, administrators have access to a new page to Configure

Internal Review Fields (Suppliers > Configuration Settings).

• This page lists all the available supplier fields that can be synced to the ERP system.

• No fields are selected by default.

• Select which fields you would like to trigger the ADW Workflow rule when data changes.

• A user must have Manage Registration Configuration permission to see this page.

• The new ADW rule will evaluate new changes made to supplier profile for the configured fields

and notify appropriate users to review the information. During this period the ERP will be

paused. In the last step of approval process the ERP sync will resume exporting information as

scheduled

• Note: You must contact JAGGAER to enable this feature. Changes may be required to your

Supplier Review Workflow process.


Sourcing Enhancements

This section focuses on enhancements to the JAGGAER Indirect Sourcing solution.


In 18.1, the term "Projects" has been replaced with the term "Work Groups". See Projects

Renamed to Work Groups for more information.

Sourcing Event Custom Fields

With the 18.1 release, customers are able to add custom fields to sourcing events. Customers can

also add custom fields to sourcing request templates, and sourcing request forms crafted using

those templates.

This enables them to capture and report on additional information that is unique to their

businesses. Content within these fields is available to support the routing of events within the

workflow process, and can be used to search for specific events.

The custom fields appearing on a sourcing event are determined by their integration into the event

type used to construct the event. On the new Custom Data tab of Event Types, users are able to

set display order, grouping, and whether or not the custom fields are required.

Users with permission to define custom fields are able to set the custom field name and response

type (single line text, multi-line text, numeric, yes/no, dropdown list, multiple choice, multiple

select, or date). Depending on the response type selected, users are further able to choose

response options, and whether the field can be searched on in Advanced Search. Users are also

able to add help text on custom fields if they so choose.

If a custom field or event type is edited, changes will appear on new sourcing events. Existing

events do not have their custom fields changed.

IMPACT

• Related Solutions: Sourcing




KEY POINTS OF FEATURE

• This feature is On by default but optional for use.

• New Permissions related to this Feature: Manage Sourcing Custom Fields (Permission

Settings > Sourcing > Events)


• To create a custom field, navigate to Sourcing > Templates and Libraries > Custom

Fields. Click the Create Custom Field button to begin creating a new custom field.

• Enter a Field Name, Internal Name, Response Type, and select if the field is active. Users

can also choose to add help text for the field and indicate if the field will be available to

search on in Advanced Search.

• If a field is made available for search, it is also available to be selected as an exposed

column on the Cost Savings Summary Report.

• The available response types are: single line text, multi-line text, numeric, yes/no,

dropdown list, multiple choice, multiple select, and date.

• If the dropdown list, multiple choice (pick one), or multiple choice (pick many) response

types are selected, the user will also be prompted to enter options for those response

types.

• An event's type determines the custom fields that will appear on it. To associate custom fields

with an event type, navigate to Sourcing > Administration > Manage Event Types, select

the event type, and open the Custom Data tab.

• Click the Add Group button to add a group for custom fields.

• Users can optionally insert a page break before the group. Page breaks cause the custom

fields listed under them to appear on separate pages listed under the Setup step of

sourcing events. Groups appearing before a page break will appear on the Setup page of

an event.

• Users can also set the display order of the group.

• Click the Add Field button under a group to open the Add Field to Group wizard. Custom

fields can be searched or selected from a list.

• Users can choose to make the field required.

• The custom fields added to the event type will be available for new events created with the

event type.

Make Item Quantity Field Supplier-Controlled

With the 18.1 release, users are able to assign an Item Quantity field as a vendor-supplied field on

a per-item basis.

This enhancement allows individual items and services to be properly sourced. For example, a

vendor is able to enter both the quantity and price when they respond to a Statement-Of-Work

request that requires a specific skill-set.

Making the Item Quantity field supplier-controlled is administered via a checkbox on product line

items and service line items:

• Make Quantity a Supplier Response Field - Allows suppliers to enter an amount in the

Item Quantity field. Selecting the checkbox prevents buyers from entering data in the Quantity

field.


The split-item award feature is disabled for an item when its Quantity field is supplier-controlled, as

each vendor's submission is a stand-alone option for the buyer's consideration.

Impact








• To make an item quantity supplier-controlled, navigate to the event's Items page and add or

edit a product or service line item. In the Line Item overlay, select the Make Quantity a

Supplier Response Field checkbox.

Enhanced Panel Questionnaire Analysis

With this release, users have the ability to view and export the data from panel questionnaire

results.

A new Panel Questionnaire Details tab on the event evaluation page provides a detailed view of

panel questionnaire ratings and results. An Excel spreadsheet export of the questionnaire results

allows further analysis of the data outside of the system.

Impact









• To view the Panel Questionnaire Details tab, navigate to the Supplier Responses page of an

event in Under Evaluation status. Choose to evaluate all or selected responses to view the

Award Scenario page. Click the Panel Questionnaire Details tab to open it.

• To export an Excel spreadsheet of the questionnaire results, click the Export dropdown on the

Panel Questionnaire Details tab, and select Export Questionnaire Details. The Evaluation

Export overlay displays. You can enter a description for the export, then click Submit. A link

to the Evaluations tab of the Sourcing Event Exports page displays, where you can

download the Excel spreadsheet.

Stage-to-Stage Auto-Transfer of Panel Questionnaire Questions

With the 18.1 release, users now have the option to transfer Panel Questionnaire questions from

one stage of a multi-stage event to the next. When creating a new stage of an event, an option

allows users to transfer panel-questionnaire questions to the new stage.

This improves event administration efficiency when the event manager requires the inclusion of

panel questionnaire questions, and their associated supplier responses, within the next stage of the

event. An auto-transfer of this data ensures that it will not need to be recreated within the next

stage of a multi-stage event.

Impact








• To transfer panel questionnaire questions from one stage of an event to the next, select Yes on

the field Transfer PQ Questions to New Stage? while creating the new stage.

• Transferred panel questionnaire questions cannot be edited, but they can be deleted, and

question weight can be edited.

Event-Level Conditional Questions

Event questions are used by buyers to ask questions of suppliers responding to events.


With this release, users are able to create event-level conditional questions. This allows buyers to

intelligently expose only those questions that are appropriate to each event-participating supplier,

providing a better supplier user experience when participating in events.

After creating a question on the Questions page of event setup, users can create conditional follow-

up questions, which are exposed based on responses to the parent question. Conditional questions

are available to be added to questions using the yes/no, dropdown list (pick one), and multiple

choice (pick one) response types.

Impact








• To create conditional questions, navigate to the Questions page of a Draft status event.

• Click the dropdown arrow on a question using the using the yes/no, dropdown list (pick

one), or multiple choice (pick one) response types, and select Create Conditional

Follow Up. The Add Question overlay displays.

• Make a selection in the Conditional Upon Value field, which lists the possible responses

of the parent question.

• Only suppliers who select this value on the parent question will see the conditional

question. Complete the rest of the question creation as normal.

• Conditionality is supported for up to three levels. Parent, child, and grandchild questions can

be created.

New Public Site Filters

With this release, new filter enabling settings are available in the Public Site Setting section of the

General Sourcing Settings page to allow buyers the option of exposing Work Group and Business

Unit filters on their public sites.

Enabling these filters allows suppliers to quickly target and locate appropriate events of interest.

• Users are able to choose whether or not to allow public site event filtering by work group. If

work groups are allowed, they can select which work groups to include as filters.


• If their organization uses business units, users are able to choose whether or not to allow

public site event filtering by business unit.

Impact






• This feature is Off by default but can be enabled by an organization administrator.


• To configure the new public site filters, navigate to Sourcing > Sourcing Administration

> General Sourcing Settings.

• Under the Public Site Settings heading, select the Allow Public Site Event Filtering by

Work Group and/or Allow Public Site Event Filtering by Business Unit check boxes.

• Enabling filtering by work group causes the Select Work Groups to include as Filters

link to appear. Clicking this link opens the Select Work Groups overlay to display, where

users can select which work groups to include as filters.

• With this release, event creators with access to multiple business units are able to select the

appropriate business unit association(s) for an event as they create the event.

• A user can select any, or all, business units for which an event is being created via the

Identify Related Business Units field on the Create Sourcing Event overlay.

• The field is only exposed to users who have access to more than one business unit within

an organization.

• For users with multiple business unit access, who have a business unit assignment

designated within their user profile, the Identify Related Business Units field will be

populated, by default, with that user's profile business unit assignment. The user will then

be able to add-to or change that assignment as desired.


Contract Lifecycle Management

This section details enhancements that are available in the 18.1 release related to Contract

Lifecycle Management.

Ability to Hide Inactive Contract Types

A new toggle link on contract types provides the ability to hide or show inactive contract types.

Impact

• Solutions Affected: Contract Lifecycle Management







• A Show Inactive/Hide Inactive toggle link is displayed in the top right corner of the

Contract Types column on the Contract Types page.

• Clicking Show Inactive displays inactive contract types in gray and italicized font. This is

the default setting.

• Clicking Hide Inactive hides inactive contracts.

• An inactive parent contract type is displayed if any of its child contract types are active.

Create Contract Wizard Updated

The Create Contract wizard has been streamlined from a multi-step contract creation wizard to a

single step.

Impact

• Solutions Affected: Contract Lifecycle Management








• The Create Contract wizard has been streamlined from a multi-step contract creation wizard to

a single-step.

• Users enter a contract name and a contract type on the initial entry screen.

• Once a contract type is chosen, additional fields are displayed and users can select items

such as templates, work groups, and language settings for the contract. See New Contract

Templates for Faster Contract Entry for additional information.

• When the Create Contract button is clicked, the contract is created and opens to the

contract Header page.

• The Start Date and End Date fields are no longer in the wizard. Once a contract is created,

they are displayed on the contract Header page and users can enter dates.



Renamed to Work Groups in the General Enhancements section for additional information.

Impact

• Related Solutions: Contract Lifecycle Management








New Contract Templates for Faster Contract Entry

Previously, creating a contract required that contract managers select field values and configure

settings on each contract.

In 18.1, new contract templates allow organizations to develop default configurations for

contracts by contract type. Designed to make the contract creation process faster and more

efficient, using contract templates as the starting point of contract creation can reduce the amount

of time needed to create contracts and provide consistent settings for contracts in a contract type.

Users with the appropriate permission can pre-configure as much contract information as possible

on a contract template. When a contract is created with a contract template, settings from the

template are copied into the contract, where they can be changed to suit the individual contract.

As part of this feature, Templates, which are currently used by the JAGGAER Contract Authoring

for Word app to create contract documents, are now called Main Document templates, and the

Templates tab in the Contract Template Library has been renamed to Main Documents. This

feature has not changed and is used in conjunction with contract templates: contract templates can

be used to define contract settings, and main document templates can be used to create contract

text.

Impact








• The Manage Contract Template and Clauses permission is needed to use this feature.

• Overview - Contract Templates from Start to Finish

• Contract templates allow organizations to develop default configurations for contracts by

contract type. Here is an overview of how they work:

• Contract templates are created in the Contract Template tab in the Libraries area.

• Default contract templates and amendment contract templates are assigned to a

contract type (optional).


• Users have the option to use a contract template when they create a contract and

when they create a contract amendment. The use of a contract template is a one-

time option only offered when a contract is created.

• Settings from the selected contract template are copied into the new contract and can

be modified.

• Setup and Administration

• The Template Library area has been renamed to Contract Template Library

(Contracts > Libraries > Contract Template Library) and these changes have been

made:

• A new Contract Templates tab is used to create and manage contract templates.

• The Templates tab has been renamed to Main Documents. Main document

templates are used with the JAGGAER Word app to configure contract text, and this

functionality has not changed.

• These options are used to create and manage contract templates:

• Create - Clicking the Create Template button on the Contract Template tab creates

a contract template, places it into Draft mode and opens it to the Contract Template

header page, where it can be configured.

• Contract templates look like contracts, but they have a purple bar across the top

of the screen and display "Contract Template" on the Header page.

• Many of the settings that are typically configured on a contract can be configured

on a contract template, such as choosing values in fields on the contract header,

adding attachments, or selecting notifications.

• These contract pages are not available on a contract template: Review

Rounds, Submit for Approval, Budget and Spend, Obligations, Comments,

Communication Center, Contract Family.

• These fields and tabs are not available on a contract template:

• Header - Parent Contract field

• eProcurement Setup - Pricing and Administrative Fee sections

• Applies To - Product/SKU, UNSPSC, and Fulfillment Center tabs

• Goods and Services - Non-Catalog Items and Contract Item Pricing tabs

• Users and Contacts - External Contacts section

• Main document templates and attachments can be uploaded to a contract

template and they will automatically be uploaded to all contracts created with the

contract template. Once a main document template is uploaded from the library,

it is not linked to the main document template, but clauses within the main

document are linked to clauses in the library.

This means that regular text on a main document can be customized to suit the

contract template, and the customized version is uploaded into contracts created


with the contract template. Clauses within the main document text will be

automatically updated when a contract is created with the contract template.

This could potentially create a situation where there are differences between the

main document template in the library and the main document on a contract

template.

Note: If organizations frequently update their main document templates and

want to always use the latest version, we recommend that they do not attach a

main document to the contract template. They can still use all other fields on the

contract template, which will be carried over to the contract that is created from

the contract template. When creating a contract from a contract template that

does not have a main document template, users simply select the main

document they want to use.

• Contract templates can be configured specifically for use with contract

amendments. For amendment contract templates we recommend using a

naming format such as Amend-[template name] to help identify them.

• View and Modify - Links are available on the Contract Template Library to view and

change contract templates. Changes made to a draft are not published until it is

finalized and activated:

• Clicking the View Active link next to an active contract template opens it in

read-only mode.

• The Create Draft link is used to create a draft copy of an active contract

template. Once a draft copy is created, the link changes to Edit Draft.

• The Edit Draft link is used to modify the draft copy of a contract template. It is

displayed when an active contract template is being revised and Create Draft has

been clicked.

Note: Contract templates do not have versions. There can only be an active copy and

a draft copy (if one has been created) of a contract template.

• Activate - When a draft contract template is ready to go, users Finalize and

Activate the contract template to make it the Active copy. The active version is used

to create new contracts. If activating the draft copy of an existing contract template,

the draft copy replaces the Active copy and it becomes the new active contract

template.

• Inactivate - An active contract template can be inactivated to make it unavailable for

selection. If a contract template with a draft copy is inactivated, a window displays

options for saving or discarding the draft. An inactive contract template can be

reactivated by creating a draft, then finalizing and activating it.

• Delete - There are two delete options. Selecting Delete Template will delete both the

active and draft copy of a template. Selecting Delete Draft will delete the draft copy

only.


• Copy - Contract templates can be copied by selecting Template Actions > Copy

from an open contract template.

• Contract Types have been updated to accommodate contract templates:

• These fields have been added to the contract type About tab:

• Default Contract Template - This field is used to assign a default contract template

to a contract type. The contract template selected here is displayed by default in the

Contract Template field on the Create Contract wizard when a contract type is

selected.

• Default Amendment Template - This field is used to assign a default amendment

contract template to a contract type. The contract template selected here is displayed

by default in the Contract Template field when a contract amendment is created for

a contract that uses the contract type.

• In the Contract Template Library, an asterisk in the Contract Type column indicates that

a contract template has been assigned to a contract type. Pausing over an asterisk shows

that it has been assigned as a default contract template and/or default amendment

contract template.

• The default contract template selections on a contract type also affect contracts imported

via CSV/XML and contracts created from a Sourcing event.

• Using Contract Templates with Contracts

• The Create Contract Wizard has been updated to include contract templates and it has

also been streamlined from a multi-step contract creation wizard to a single step:

• Users enter a contract name and a contract type on the initial entry screen. Once

a contract type is chosen, additional fields are displayed where users select the

templates, work groups, language and currency settings for the contract.

• This update also applies to the Create Contract wizard displayed when contracts are

created from a contract request or sourcing event.

• The use of a contract template to create a contract is a one-time option only offered

when a contract is created. The use of a contract template is defined by these two fields

on the Create Contract wizard:

• The Use Contract Template field determines whether or not a contract template is

used to create a contract. Users select Yes to use a contract template or select No if

they do not want to use a contract template. If a default contract template has been

assigned to the contract type, this field is set to Yes by default. If there are no active

contract templates for the contract type selected, the Use Contract Template field is

not displayed.

• The Contract Template field is used to select a contract template. The contract

template assigned to the contract type is displayed by default, but users can select

another contract template. Only contract templates configured for the contract type

and that belong to a work group that the contract creator has access to are available

for selection. This field is only displayed if Yes is selected in the Use Contract

Template field above.


• If a contract template is selected, the settings from the contract template are copied into

the new contract. They are a starting point for contract configuration and can be changed

on the new contract.

• Using Contract Templates with Contract Amendments

• These fields in the Amend Contract window affect the information that is copied into a

contract amendment:

• The Use Contract Template field determines whether or not a contract template is

used to create a contract amendment.

• If Yes is selected, an additional field is displayed:

• Contract Template - This field is used to select a contract template. The

amendment contract template assigned to the contract type is displayed by

default, but a different contract template can be selected.

• If a contract template is selected, settings from the template are copied into the

contract amendment if they do not affect values from the previous contract. If

there is a discrepancy, values on the previous contract have priority. Values

from the previous contract supersede values from the contract template.

• The Include the latest attachment versions? field determines whether the latest

version of contract attachments from the previous contract are copied into the

contract amendment.

Note: If a contract template is selected and this field is set to Yes, the contract

amendment will have the Main Document from the amendment template along with

any other contract attachments on that template. In addition, it will bring over the

Full Contract PDF/Fully Executed PDF and any attachments from the previous version

other than the Main Document (as this is part of the Full Contract PDF/Fully Executed

PDF).

• A Full Contract PDF or Fully Executed PDF copy of the previous contract is added as

an attachment to the contract amendment with the Print with Full Contract option set to

Yes, unless both the Use Contract Template and the Include the latest attachment

versions? fields are set to No.

• Contract Requests have been updated to accommodate contract templates:

• When creating a contract from a contract request, the Create Contract wizard provides the

option to use a contract template to create a contract from a request. If a contract

template is selected, values entered on the contract request supersede values from the

contract template.


• Sourcing contract fields have been updated to accommodate contract templates:

• When creating a contract from a sourcing event, the Create Contract wizard provides the

option to use a contract template to create a contract. If a contract template is selected,

values entered on the sourcing event supersede values from the contract template.

• Contract CSV Import and Contract XML Import have been updated to accommodate

contract templates:

• A new UseDefaultContractTemplate column has been added to the Contract CSV and

XML import files. It determines whether or not a default contract template is used to

populate fields on new imported contracts. This field is only used for imports and is blank

on exports:

• For new contract imports:

• If set to Yes and fields on the imported file have values, the values from

imported file are used.

• If set to Yes and fields on the imported file do not have values, values from the

default contract template assigned to the contract type are used. A warning

message will indicate if there is no default contract template assigned to the

contract type.

• If set to No (default setting), the system will disregard the default contract

template and only use values from the imported file.

• For updated contract imports:

• The system will disregard default contract templates and only use values from

the imported file. A warning message will indicate if an import row is an update

and not a new contract.

Important! If an organization uses contract import or export files to integrate with other

internal systems, the change to these files may cause issues with that integration. Please

check with your system administrator to determine the impact of these changes.

New Contract Communication Center

In 18.1, a new Communication Center section has been added to contracts to allow

organizations to record and monitor email correspondence about a contract from one central

location within it. As part of this feature, a new Send Email contract action allows users with the

appropriate permissions to send emails from a contract within Contract Lifecycle Management.

The Communication Center displays emails sent via the Send Email contract action and emails sent

during an external review round, along with all replies in the email conversation. Users can view,

add, edit or delete email recipients in an email conversation.

In addition, as part of the new Ability to Compare Documents feature, this area allows users to

compare an email attachment to the latest version of a contract main document or another

contract attachment, as long as both files are Microsoft Word files attached to the same contract in

a .docx format.


Impact







• New Permissions related to this Feature: Email from Contract (Permission Settings >

Contracts > Contracts Permissions) - Users with the permission can see Send Email and

View/Reactivate Subscriber options in the Contract Actions menu. They can also see the

Send Email button on the Communication Center page. This allows them to send emails from

a contract, and view email recipients who have unsubscribed from a contract email

conversation and reactivate their subscription. Without the Email From Contract permission, a

user can still send emails through the external review round process and these emails and any

replies will show in the Communication Center. Internal review rounds are not included in the

Communication Center since emails are sent by Notification Preferences.

Important Note: Emails sent using the Send Email contract action or during an external

review round are visible to all recipients of the email and anyone who can access the

Communication Center page of a contract. The information displayed includes email recipient

names and email addresses, the original email text, and all replies to the email.

• To help ensure the deliverability of email messages using our new Communication Center

feature, please have your IT Department add our domains to your company’s white list.

• A new Communication Center section has been added to contracts:

• General information:

• Emails sent using the Send Email contract action are displayed here.

• Emails sent during External Review Rounds are displayed here. Emails sent from

external review rounds will be tracked starting from the 18.1 release date. Emails

sent prior to that date will not be recorded. Emails sent through the external review

round process and any replies will show in the Communication Center. The Email

From Contract permission is not needed to send emails from an external review

round. Internal review rounds are not included in the Communication Center since

emails are sent by Notification Preferences.

• An email and all of its replies is referred to as a conversation.

• The Communication Center page is visible if users have access to the “Full Contract

Details” as indicated in Work Groups > Contract Users tab.


• The dates and times that emails were sent and received are displayed in the user's

preferred time zone.

• History pages record all changes.

• There are two pages in the Communication Center:

• Communication Center (main page) - Clicking Communication Center in the left

menu of a contract opens a page that lists all the emails that have been sent via the

Send Email contract action or during an external review round. Columns show when a

conversation started, the number of messages (responses) in the conversation and

the last update.

• A Send Email button allows users with the Email From Contract permission to

send an email directly from the Communication Center page.

• A icon indicates that there are attachments on email messages.

• Conversation Details (second page) - Clicking on a conversation row in the main

Communication Center page opens a second page that shows the original email text

and all replies, the recipients and their email addresses, and any attachments

included in the email. The following options are also available on this page:

• A Subscribers: section lists all recipients in an email conversation. Active

subscribers are displayed in blue text. Recipients who have unsubscribed are

displayed in gray text. Clicking on a recipient name displays their email address.

• A Change Subscribers button provides the ability to add, edit or remove

subscribers (email recipients) in an email conversation:

• Add - New email recipients can be added to an email conversation at any

time. They will receive the next and subsequent emails in the conversation.

This option cannot be used to add individuals who have unsubscribed to a

contract's emails.

• Edit - Clicking on the name or email address of a subscriber opens the fields

for editing. Users can make changes, then click the green checkmark to save

the revisions.

• Remove - Removing a subscriber from a contract email conversation means

the individual no longer receives emails in that specific email conversation.

They can be added to new emails sent from the contract.

• A Messages section shows the original email text and all replies.

• An Add to Conversation button allows users to send a reply to all recipients in

the conversation. It opens a Send Email window with no recipients, as the reply

will automatically be sent to all active subscribers.

• An Actions > Compare With option is displayed next to each email that has an

attachment. It allows users to compare attachments received via email to the

latest version of contract documents on the Attachments page. See New Ability to

Compare Documents.


• The Contract Actions menu has been updated. New Send Email and View/Reactivate

Subscribers options are available to users with the Email From Contract permission:

• Send Email

• The Send Email contract action is used to send emails from a contract. It is

displayed on all contract pages of contracts in any status. The emails and their replies

are saved and can be accessed from a contract's Communication Center page.

• Clicking Contract Actions > Send Email opens a window where users add email

recipients, choose the contract attachments they want to include in the email (or

upload attachments from their local drive), and enter the subject and text of the

email. Formatting options provide the ability to insert placeholders and links into the

body of the email.

• When email recipients reply to the email, all recipients receive the response, and the

entire conversation can be viewed in the Communication Center.

• Email recipients can Unsubscribe or Subscribe to emails sent from a contract.

Note: Email recipients unsubscribe from or subscribe to a specific email, but the

settings are applied to the entire contract and will affect whether or not they receive

new emails sent from the contract.

• If an email recipient selects the Unsubscribe link in the footer of a contract

email, they no longer receive emails for that contract. This includes future emails

in the conversation and new emails sent from the contract.

• In the Communication Center, their name is displayed in gray text in the

Subscribers section on the Conversation Details page of the email

conversation and their name is also listed under "Select Subscribers to

Reactivate" in the new View/Reactivate contract action.

• Unsubscribed email recipients can click the Subscribe link in the footer of a

contract email to return to email conversations in the contract they unsubscribed

from. They will receive the next and subsequent emails in the email conversation

and new emails sent from the contract. Note: Email recipients will not be added

back to a conversation even after clicking Subscribe if they have been removed

from that conversation.

• In the Communication Center, their name is displayed in blue text in the

Subscribers section on the Conversation Details page of the email

conversation they subscribed to.

Note: If organizations wish to prevent a user from re-subscribing to a contract

email, they must be removed from each email conversation in a contract via the

Change Subscribers button. The new Communication Center section in Advanced

Search can be used to find email recipients.


• View/Reactivate Subscriber

• The View/Reactivate Subscriber contract action is used to reactivate the

subscription of email recipients who have unsubscribed to a contract's email

conversations.

• From a contract, selecting Contract Actions > View/Reactivate Subscribers

displays a list of the individuals who have unsubscribed to the contract's email

conversations. Selecting the checkbox next to a recipient name and clicking the

Reactivate button reactivates their subscription. They will receive the next and

subsequent emails in the conversation, and new emails sent from the contract.

• In the Communication Center, their name is displayed in blue text in the

Subscribers section on the Conversation Details page of the email conversation

they subscribed to.

• Contract Advanced Search

• A new Communication Center section has been added to the contract Advanced Search

page. Search filter fields allow users to search for contracts with email conversations by

sender or email recipient names, email addresses, or dates.

• Returned Emails

• If an email does not get through to a recipient, the sender will receive an email listing the

recipients who didn't get the email, and a message on the Communication Center Details

page will indicate that the email was not sent to the recipient(s).

• Consortium Contracts

• Contracts that have been published from a parent to a member org do not have a

Communications Center page or a Send Email contract action. Contracts in parent

organizations will have the Communication Center page if they have Contract Lifecycle

Management.

New Ability to Compare Documents

A contract may go through many iterations as it is being developed and throughout its lifecycle. In

18.1, a new Compare Documents feature allows users to view two contract Word documents side

by side in Contract Lifecycle Management, and compare the differences.

Differences between the two documents are highlighted to help users identify what has changed.

The documents being compared must be Microsoft Word files attached to the same contract in a

.docx format.

This feature encompasses two areas of Contract Lifecycle Management:

• On the contract Attachments page, users can compare two versions of the same contract

document. They can compare two versions of the contract main document or two versions of

an attachment.


• In the new Communication Center, users can compare an email attachment to the latest

version of a contract main document or another contract attachment. When a comparison is

generated, an Apply Changes in Word option allows users to open the JAGGAER Contract

Authoring for Word app to continue authoring the document. For example, this option can be

used to accept or reject changes in Word, then upload the revised version. If there are

placeholders in the compared documents, an additional View Placeholder Differences

window displays the current and proposed values of placeholders in the compared document.

Impact








• General Information

• The documents being compared must be Microsoft Word files attached to the same

contract in a .docx format.

• Deleting a contract also deletes any compared document files.

• Compare two versions of the same document

• The Attachments page of a contract is used to compare two versions of the same

document. There must be at least two versions of the attachment being compared.

• Clicking Actions > Version History next to an attachment opens the Version History

window, where all versions of the document are displayed at the top of the page.

• In the Version History window, users click the Select button next to each version of the

document they want to compare. Once a document version is selected, user can click

Deselect to remove it from selection.

• In the Compare Section area on the bottom of the page, the first document selected is

displayed on the left and the second document selected is displayed on the right. The

icon can be clicked to have the documents switch places.

• Once the Compare button is clicked, a new browser tab opens and displays the compared

documents side by side.


• Compare an email attachment to a contract main document or a contract attachment

• The Communication Center of a contract can be used to compare an email attachment

to the latest version of a contract attachment.

• Users open an email conversation with attachments by clicking on the conversation row

to open the Conversation Details page, then selecting Actions > Compare With next

to the email that has the attachment they want to compare.

• In the Compare Email Attachment window, users select documents they want to

compare in these fields:

• Select email attachment - Users select an email attachment.

• Compare with - Users select a contract attachment by selecting these options:

• Main Document - Select to compare the contract main document to the email

attachment.

• Contract Attachment - Select to compare a contract attachment to the email

attachment. If this option is selected, the Select Contract Attachment field

displays a list of contract attachments that users can choose from.

• When the Compare button is clicked, a new browser tab opens and displays the

compared documents side by side.

• Compared Document Results

• Once a comparison is generated, the two documents that are being compared are

displayed side by side in a new browser tab, in read-only mode. Differences between the

two documents are highlighted in yellow and color-coded:

• Click the icon at any time to have the documents switch places.

• Red blocks along the left margin show which areas have changed.

• Text that has been changed or added is highlighted in yellow.

• Text that has been deleted is highlighted in yellow, red and crossed out.

• View Placeholder Differences and/or Apply Changes in Word

• When comparing an email attachment to a contract document, an Actions menu allows

users to open the compared files as one document in the JAGGAER Contract Authoring for

Word app, where they can continue to author the document and upload the revised

version into Contract Lifecycle Management. Documents with placeholders have an

additional option to view placeholder differences.

• From a generated comparison:

• If the compared documents do not have placeholders, the Actions button displays an

Apply Changes in Word option that can be selected to generate a Word document

and open it in the Word app.


• If the compared documents have placeholders, the Actions button displays a View

Placeholder Differences option. Selecting it opens the Placeholder Differences

window, which shows the current and proposed values of placeholders in the

compared documents. From there, the Apply Changes in Word button can be clicked

to generate a Word document and open it in the Word app.

• When Apply Changes in Word is selected, the system generates a Word file that

combines the two compared documents into one (temporary) file. Clicking on the

generated file opens it in the Word app and the document is automatically checked out to

the user.

• In the Word app, users can accept or reject changes in the REVIEW tab using Word's

reviewing features. Additional changes can be made as needed.

Note: We recommend using the All Markup setting in the REVIEW tab in Word to display

the proposed changes.

• When changes to the proposed document are complete, clicking Check In uploads the

revised document into Contract Lifecycle Management. It becomes the latest version of

the document, and the version number increases by one.

Word App Extended

Previously, the JAGGAER Contract Authoring for Word app was used to create contract main

documents that contain contract text.

In 18.1, enhancements to the JAGGAER Contract Authoring for Word app allow users to create

documents with the Word app that are separate from the contract main document. The documents

are saved as contract attachments on the contract they are created in, and can be downloaded as a

single document or included as part of the contract in the "Full Contract as PDF" document.

This update allows users to leverage Word App features such as placeholders and clauses to create

stand-alone documents that contain contract data, such as a contract summary page.

Impact









• On the contract Attachments page, the Add Attachments window has been updated:

• A new Create a Blank Word Document for Me option has been added to the

Attachment Type field. Users can select it to create a Word document using the

JAGGAER Contract Authoring for Word app:

• Users enter a File name and complete the Print Order, Print with Full Contract and

Contract Summary Visibility fields to define its use on the contract.

• When Save Changes is clicked, a Word document is created and added as an

attachment to the contract.

• The document is opened in the Word app by clicking the file link or selecting

Download from the Actions menu next to the record.

• In the Word app, users can check out the document, add text, and insert placeholders

and clauses as desired.

• Clicking Check In saves changes to the document. Users have the option to keep the

document checked out to themselves or check it in to allow other users to modify the

document.

• The "File" option on the Add Attachment window has been renamed to "Add My Own".

This option allows users to add an attachment to a contract by uploading a file from their

desktop.

• The following placeholders have been added to the Placeholders tab of the Word app:

• Contract

• Contract Managers (explicitly named contract managers)

• Summary (this is the Summary field on the contract header, displayed in plain text

only)

• Renewal

• Auto-Renew

• Budget (new section)

• Budget

• PR Spend

• Lifetime PR Spend

• Lifetime Member PR Spend

• PO Spend

• Lifetime PO Spend

• Lifetime Member PO Spend

• Invoice Spend

• Lifetime Invoice Spend

• Lifetime Member Invoice Spend


Contract Request Template Versioning

Previously, making changes to an active contract request template required it to be archived,

then copied, revised and finalized before it became the new active contract request template.

In 18.1, versioning has been implemented for contract request templates as part of the contract

request templates as part of the Form Request Template Versioning enhancement. Users can

modify a contract request template without affecting the active version and publish it when

changes are complete.

Previous versions of contract request templates are accessible, and an indicator shows which

version is the active contract request template in use.

Impact








• Contract request templates now move through the following stages for creation and revision:

• When a contract request template is first created, it is placed into Draft status and the

draft version can be saved, changed or deleted until the template is ready to be used. The

Draft status only occurs upon initial template creation. When the initial draft version is

finalized and activated it becomes the Active version and can be used to create contract

requests. On the Manage Contract Request Templates page, "Finalized" is displayed in the

Status column and "Version 1" is displayed in the Active Version column.

• If changes are needed to an active contract request template, the Edit Draft action allows

users to make changes to a draft copy of it. Changes can be saved, but not published, by

clicking Save Progress or Next while in the draft contract request template. When the draft

is finalized and activated, it replaces the existing version of the contract request template

and becomes the active version in use.

• A new Edit Draft action is available on the Actions menu of a finalized contract request

template. It allows users to revise a draft copy of an active contract request template:

• Click Action > Edit Draft to open the draft copy of an active contract request template.

• Changes to the draft copy can be saved, but not published, by clicking Save

Progress or Next in an open contract request template record.


• Clicking Edit Draft always opens the latest version of the draft copy of a contract

request template, which contains all the changes that have been saved up to that

point.

• When the changes to the draft copy of a contract request template are complete, users

Finalize and Activate the template to replace the currently active contract request

template with the updated copy, and it becomes the active version used to request

contracts. The number in the Active Version column on the Manage Contract Request

Templates page increases by one.

• A Choose Other Version link is displayed in the top right corner of a contract request

template if there is more than one version of it. It shows all the versions of the contract

request template and clicking on a version will open it. "(Active)" is displayed next to the

finalized and active contract request template that is currently in use.

• The Manage Contract Request Templates page has been updated.

• A new Active Version column indicates which version of a contract request template is in

use.

• The Description column has been renamed to Version Description.

• The Status column indicates whether a contract request template is in one of these

statuses:

• Draft - A Draft status is only displayed if a contract request template is a new record

that has never been finalized (i.e., there is no active version).

• Finalized - Indicates the contract request template is active and users can use the

template to request contracts.

• Archived - Archived contract request templates cannot be used to request contracts

and are only displayed if the Show Archived Contract Request Templates checkbox is

selected. They can be reactivated by editing the draft copy, then finalizing and

activating it.

• The Created column displays the date that the contract request template was created.

• The Last Updated column displays the date that the active contract request template was

last finalized and activated.

New Fields on Contract Export

New fields have been added to contract CSV, XML and Excel export files to provide data for

terminated contracts.

Impact









• The following columns have been added to contract CSV, XML and Excel import/export files to

provide reporting data. These fields CANNOT be updated through import.

• Termination Date - Displays the date and time that a contract was terminated.

• Termination Reason - Displays the termination reason entered when the contract was

terminated. Note: Only contracts terminated after the 18.1 release date will display a

termination reason.

Important! If an organization uses contract import or export files to integrate with other

internal systems, the change to these files may cause issues with that integration. Please

check with your system administrator to determine the impact of these changes.


Savings Management

This section focuses on enhancements to the JAGGAER Indirect Savings Management solution.



Renamed to Work Groups for more information.