TABLE OF CONTENTS

• Introduction
• Step 1: Create a Config
• Step 2: Fill out key information for Config and save it
• Step 3: Fill out / edit details relating to the config (tabbed wizard)
  • Tabbed wizard page: Schedule Selection
  • Tabbed wizard page: Direct mapping
  • Tabbed wizard page: Value transformations
  • Tabbed wizard page: Host System Parameters (HSP)
• Testing the Config formulas against randomized data
• Copying a config
  • Make a copy of an existing Config
  • Copy the definition of a Config to clipboard and its 2 use cases
    • Use Case 1: Replicate a config from one of your environments (Test) to another (Prod)
    • Use Case 2: Send the definition of a config to a collaborating partner
  • Example of Confg definition in JSON format

Introduction

The last step for the Setup users before ILAP Exchange agreements (IEAs) can be created, is to create Configs. This can be done after the Template and the Connector, that will be used on this Config, have been created. These three steps form the main responsibilities in the Setup admin role.

Matching Configs on the Owner and Partner side need to be created before users can create an IEA. This means that one of the two needs to create a sending config, and the other a receiving config. The rest of the process is identical for both sides. This article describes how it is done.

Creating configs in the context of the Setup user role.

Step 1: Create a Config

Go to the Configs page from the Setup Menu and click on the button: “+ New config”.

The Configs page with the setup menu and the “+ New config” button shown (1) together with other numbered items in form, described below:

What elements are shown in Configs form and what columns are shown in grid?

Step 2: Fill out key information for Config and save it

A wizard form will ask you for some basic key information regarding the Config you want to create:

Title: The title (name) of the Config. Best practice in case you are making both the sending an receiving configs: Suffix the name with "_s" for sending and "_r" for receiving, then you can see these configs as pairs if you sort on Title in grid.

Template: The name of the Template to use.

Connector: The name of the Connector to use.

Direction: Specify if this is a Sending of Receiving config

Labels: Optionally, you can add labels to tag the Config so it is easier to identify later.

Wizard page when creating a new Config

When you press "Submit", the Config will be saved under status "Being created".

The next steps (see Step 3 below) are aimed at specifying or editing Config details (using a tabbed wizard):

- What schedule(s) it applies to

- What direct mapping to use when populating a Template field...

- ... or what formula to use (including setting up value maps)

- What specific parameters to set for the selected host system (used as default settings in IEAs using Config).

Step 3: Fill out / edit details relating to the config (tabbed wizard)

Here you can move through the 4 steps in the tabbed wizard (where you can either press "Save & next" or press the tab directly that you want to edit data for), and specify the details for each step.

Before going into each of these, let's dwell for a moment on the "red numbers" that describe the elements seen in the form:

Setting up details for a Config, using the tabbed wizard. See below for explanations of elements.

Explanations of form elements shown in red numbers above:

Item	Description
1	Edit the Title of the Config.
2	A row of key values, specified in Step 2, that will be remain editable until the Config is published - after that these will be read only.
3	The 4 tabs for the tabbed wizard described in more detail in next 4 subchapters.
4	Close button: If pressed, you will loose any changes you have made after last save.
5	Delete button: If pressed and the Config is in use by an IEA, you will get a popup screen warning you of consequences of deleting it. If you then press "Delete" it will be permanently deleted:
6	Save button: Press if you want to save current work in Config.
7	Save & next button: Save and move on to next tab in wizard. If you have reached the rightmost tab, the text of the button will change to "Publish". The config is now available for use by one or more IEAs.

Tabbed wizard page: Schedule Selection

One of more schedules need to be selected (in checkboxes at left of each row), but note that once you select the first schedule, many (or all) of the other schedules will become "gray" and cannot be selected. The reason is that only schedules with the same "Code set ID" can be selected in a Config. This Id indicates which "user field set" that the schedule uses (or "code sets" as they are sometimes referred to).

When using a P6 Connector, you will by default use only the Global Activity Codes (and not the Project specific ones), so they will therefore have a blank Code set ID, indicating that there is no differentiation between schedules regarding user fields. The good news is then that you can make a config using ALL schedules in the list, making it highly reusable.
On the other hand, if the P6 Connector used in a config has enabled the checkbox called "Include project level activity codes", then each schedule will have its own custom set of user fields, and you will then see "Code set ID values" in your list of schedules. A config can then only apply for one schedule.

SAP is another system where Code set ID is blank, since the concept of user fields is not supported there.

Selecting one or more schedules sharing the same user field set (Code set ID)

Options for filtering the schedules in list

The schedule filter in screenshot above allows you to (1) only show schedules with same Code set ID as the selected schedule, or (2) have a finish date that has not yet passed (i.e that they are still active)

Tabbed wizard page: Direct mapping

The "Direct mapping" page is where you directly assign a Host field in the source system to an ILAP term in the used Template (in the case of a sending Config), or assign which Host field that the ILAP Term's value should be passed on to in the receiving schedule (in the case of a receiving Config).

Screenshot below shows the column in red "box" where the Host fields dropdown allows you to choose which field to choose from. In the example (at 3) you see that each ILAP term relates to a specific schedule "level" (Schedule or Activity), and the dropdown will reflect different fields for each of these levels. In fact, you can see in (1) and (2) that the same host field exists (in Safran) for both Schedule and Activity level (fieldname is "description"). 

Direct mapping implies selecting which Host system field should correspond to which ILAP Term in Template.

Tabbed wizard page: Value transformations

In case you need to make some kind of transformation of a value, you need to select the "Use Value Transformation" (seen in screenshot above), in which case it will disappear from the "Direct mapping list" and instead appear in the "Value Transformation" list:

The items marked in previous tab with "Use Value Transformation", will show up in this tab, and a formulas (1) needs to be created by you (or in case of pressing the "+Add" at column (2), it will automatically be created for you).

The form that opens when clicking the "edit pen" in (see 1 above) is described in detail in this article, and needs to be studied carefully before proceeding with making formulas. It also describes the process of creating and editing value maps (2) above.

Tabbed wizard page: Host System Parameters (HSP)

The UI for defining HSPs are different for each Host System (i.e planning system such as Safran, P6 MS Project, SAP). In fact, it is different from sending and receiving configs even for the same Host System. A list of complete descriptions for each of the Host systems and Sending/Receiving direction is found here.

HSPs will act as default values when creating an IEA, and may be changed (overridden) there relative to the Config values. For this reason, changes made to HSP in a Config will NOT signal any "Update" status for the IEA using it - this status will only result from changes made to the other 3 tabs in the wizard:

Testing the Config formulas against randomized data

There is a very useful option in the Options menu called "Formula result preview":

This will allow you to test all your formulas against some randomized (but editable) schedule data. Note that the "Test schedule data"-tab (see screenshot below) contains a "mini schedule" in JSON format, with one activity and all of its related properties (including one resource assignment and one link - called successor in the JSON). This "one activity"-schedule will be applied to all of your formulas and shown as a separate row in the "Preview Result" tab's grid, where the resulting value can be seen in column "Result", and the status (error or not) can be seen in column "Status".
In fact, also the Direct Mappings will show up in this list - but all having the formula "[VALUE]" (which is in fact what direct mapping is - passing on the value with no change to it):

The preview result for each formula against the one (randomized) activity.

Here is an example of the Test schedule data. You can edit any setting including removing any row, which can be very useful when testing the formulas' resilience against null values.:

The Test schedule data can be modified (and saved for later use) so that you better can predict the result of your formulas.

Copying a config

There are 2 different ways you can "copy" a Config:

1. If you want to make a copy of an existing one.

2. If you want to "send" information to someone you collaborate with so that they can recreate a Config (semi-manually).

Make a copy of an existing Config

In the Config overview table, you will see a choice under the "three dots" menu called "Duplicate":

You will then be able to change the Title and .....

Copy the definition of a Config to clipboard and its 2 use cases

When selecting the option below, the selected Config definition (JSON) will be copied to your clipboard. 

This feature may be useful in the following cases, described in separate two subchapters below:

Use Case 1: Replicate a config from one of your environments (Test) to another (Prod)

Follow these steps:

1. Create a new Template in Prod and give it the same Title as in Test.

2. Create a new Config in Prod of the same type (i.e "Sending" or "Receiving") as in Test.

3. Save the Config and close it.

4. Reopen the Config, and select "Option - Paste from clipboard". Any problems that occur during the paste operation will be shown in a pop-up windown so that you can get an understanding of how to mitigate the problem. Examples: An ILAP Term in your new Template may not have the same name as in the original, or the connector used had a different name.

Use Case 2: Send the definition of a config to a collaborating partner

Prerequisite: You and your collaborating partner need to have a shared understanding of the Host fields your schedule will be using, so that the names (Host Field name and alias) will match the config definition you are sending to them.

Create an email and type these instructions:

1. You will be given a shared template called X. (<- share your template with person's tenant if in another organization - if in same organization then skip this step in the instructions!)
2. Create a new config of type "Sending" or "Receiving" (<- remove the one that does not apply),  and give it a title and schedule Id of your choice, while choosing Template X. Select a connector that has the same Host fields as has been previously agreed upon.
3. Save the Config and close it.
4. Copy the json contents given in this mail (<- you will have to paste the contents of your clipboard in mail)
5. Reopen the Config and selelect "Option - Paste from clipboard". Please observe any warnings given that indicate if you need to do any manual changes due to inconsistencies found during paste.

Example of Confg definition in JSON format

Below is a formatted view of the JSON (which would otherwise be difficult to read):

{
  "id": 123,
  "connectorHostSystem": 2,
  "connectorName": "Safran 6007",
  "direction": 0,
  "directionText": "Sending",
  "mappings": [
    {
      "name": "OG_Act_Discipline",
      "description": "The Discipline code for the activity. Typically one character. Example: E=Electro",
      "dataType": 18,
      "planningObjectType": 2,
      "hasDirectMapping": false,
      "allowContentControl": true,
      "allowBlank": true,
      "mappedConnectorHostFieldName": "uf_text1 (Responsible)",
      "formula": "VM.Map_OG_Act_Discipline_U.Map([VALUE])",
      "contentControlLevel": 12,
      "isConfigTemplateFieldMapping": true,
      "isCoreFieldMapping": false,
      "valueMaps": [
        {
          "templateValue": "",
          "value": "Atle",
          "description": "",
          "fieldValueText": "Atle Kaland",
          "fieldValueDescription": ""
        },
        {
          "templateValue": "",
          "value": "Erik",
          "description": "",
          "fieldValueText": "Erik Danielsson",
          "fieldValueDescription": ""
        }
      ]
    },
    {
      "name": "OG_Act_AreaDescription",
      "description": "The descriptoin of area assigned to the activity",
      "dataType": 18,
      "planningObjectType": 2,
      "hasDirectMapping": false,
      "allowContentControl": false,
      "allowBlank": true,
      "mappedConnectorHostFieldName": "description",
      "formula": "\"Values from Source || \" + [VALUE].ToLower()",
      "contentControlLevel": 12,
      "isConfigTemplateFieldMapping": true,
      "isCoreFieldMapping": false,
      "valueMaps": []
    },
    {
.....
.....