Fall 19 Release Notes

Enhancements to Application Behavior

Planning

• Reset a scenario and all its associated templates and entities to an In Progress state by using the Reset All button.

• Undo an action on a template/budget entity by using the Recall option.

Reporting

• When the Dynamic Report format and styling functionality is enabled, the font format and size of the following fields are modified:

  • Formula Bar

  • Report Title

  • Grid Headers

  • Grid cells

  • Header and footer section

  • Drill Through data

Also, the grid alignment, freeze pane, status bar, and scroll bar are enhanced for usability.

• The indent spacing is modified based on the member hierarchy level in the existing dimension based Dynamic Reports. The indent spacing is only visible if the Suppress Indent checkbox is not selected.

• The font size of Insert Format, Header, and Footer is retained when you save a report. The font size is not altered even if you enable or disable the functionality.

• When a Static or Dynamic Report Set is used on the row axis of a Dynamic Report, the primary dimension which is used in the Report Set is reflected as the column header in the report. This is also applicable to the Dynamic Report Set used in combination with other Report Sets and dimensions.

• The format and style for the Dashboard export are modified.

Modeling

• The enhancements to the Spotlight Web interface for Views are enabled by default in the application.

Data Integration

• When you save the Translations Line Setup without making any changes, a notification is displayed that there are no changes to save.

• Audit Log displays detailed information about the Translation Lines Setup changes. The existing values are displayed in the Old Value column and the updated changes are displayed in the New Value column. This is applicable for a newly created or an edited Translation line setup and will not work for deleted Translation line setup.

• If the Process Employees checkbox is selected, a task is triggered for Employee Process after successful data load. The task to process all the employees will be submitted only if the Enable Delta Processing is enabled in the Define Detailed HR Budgeting Criteria page of Configuration Tasks.

Platform

• Audit Log displays detailed information about the Hierarchy Management changes. The existing values are displayed in the Old Value column and the updated changes are displayed in the New Value column.

Planning: Bulk Export and Upload of Approval Roles and Budget Entity Permissions

This enhancement expedites the modification process of Approval Role Setup. You can use the feature to directly upload the approval roles’ information in XLSX format to the Approval Role Setup page.

We have created a sample template that you can download and use while uploading approval roles. You can download the sample template, enter hierarchy and approval role details, and then upload multiple approval roles and changes with one click of a button.

Approval roles and budget entity permissions can also be exported simultaneously by using three different options: Export All Users, Current Users, and Export Selected Users. You can then edit the data in any of the downloaded files and upload the same file directly back to the application.

In Practice: Export Approval Roles and Budget Entity Permissions for a Single User/All Users

1. Go to Maintenance > Admin > User Management > User tab.

2. Click More and then select Approval Role Setup.

3. Click the Export drop-down list. A list of options appears.
   

4. You can perform any one of the following actions:

   • Click Export All Users to export the approval roles and budget entity permissions of all the users in the application.

   • Click Export Current User to export the approval roles and budget entity permissions of the user currently selected in the User list box.

     

   • Click Export Selected Users to export the approval roles and budget entity permissions of the users selected in the Export Selected Users window.

     

     The ApprovalRoleExport excel file is downloaded with the required approval roles.

     

5. Make the required changes, and then click the Import icon to upload the file. For more information about the Import functionality, refer the In Practice: Import Approval Roles section.

   

In Practice: Import Approval Roles

1. Go to Maintenance > Admin > User Management > User tab.

2. Click More and then select Approval Role Setup.

3. Click the Import icon. The Approval Role Upload dialog box appears.

   

4. Click Download Sample Template. It is important that you use the sample Excel template, because it instructs you how to organize your data and load it back into the application successfully.

   

5. After the template has been downloaded to your computer, open the template.

   

6. The template displays the required fields. Also, this template provides information about how you can enter the correct data in all the fields.

   

7. Enter the relevant details in the User ID, Approval Role, Member Type, Level 1, Level 2, and Level 3 columns according to the instructions provided in the sample template. Ensure that you delete all the instructions in the sample file before uploading it.

 The following table describes the columns in the sample template.

The following table contains sample data for the columns in the sample template.

1. Save the XLSX file to your computer.

2. In the Approval Role Upload dialog box, click Choose File.
   

3. Browse for and select the XLSX file that you saved to your computer.

4. Click any one of the following options from the Upload Actionsfield:

   • Overwrite: To overwrite all the existing levels and approval roles. Or, to overwrite a specific level or overwrite specific approval roles. To do so, you can download the file for a specific user and update the required levels/approval role, and then upload the file to replace the existing data for this user with the data in the uploaded file.

     Note:

     If you want to overwrite specific levels or overwrite specific approval roles, it is important that you download the ApprovalRoleExport excel file by using the required option from the Export drop-down list.

   • Append: To update the existing approval roles and to add additional levels with approval roles.

5. Click Upload.

   

6. After the file has been uploaded, a confirmation message is displayed. Click through to the Detail View dialog box (as shown here) to view the status of the upload action. Additionally, a process called ApprovalRolesUpload is created on the Job Manager page (as shown here).

   

   

7. If the upload process failed or was completed with errors, select the Click Here link under the Status column of the Detail View dialog box. This action downloads an Excel file with detailed information about why the failure occurred.

   

   An example of a failed upload process is shown here. Fix the errors and upload the file again.

   

   After the approval roles have been uploaded successfully, a confirmation message is displayed. The uploaded approval roles are displayed on the Approval Role Setup page, as shown here.

   

Best Practices

• To make permission management easier, you can use the user export options. If you use this feature, you do not have to worry about the format; you can just make the necessary changes to the exported information and quickly reload the file.

• You can use the Overwrite functionality to replace data. If you want to completely remove the existing data and replace it with new data, use the Overwrite option; otherwise, you can just use the Append option.

• If you are a bit hesitant to use this functionality, you should try out this feature in your sandbox environment. After you are familiar with the functionality, you can make any changes to the Approval Roles or Permissions on your production environment.

Planning: Enhanced Workflow Updates for Send Back and Recall

We have introduced an option named Recall to help users undo their actions, if actions are performed in error on entities and templates. We have also enhanced the existing Send Back option to allow additional flexibility.

Recall is the reversal of personal actions by a user who performed the action, as long as a user with a higher-level privilege does not act on the entity or template before it can be reversed.

Send Back enables users to send entities or templates back for any changes, and users get notified if a template or entity is sent back.

For more information on these enhancements, refer to the following sections:

Ability to Recall Templates/Budget Entities after Forwarding, Approval, and Final Approval

Enhanced Send Back Action for Templates/Entities

Availability of Send Back and Recall options for users with a detailed example

Ability to Recall Templates/Budget Entities after Forwarding, Approval, and Final Approval

This functionality is now enabled by default for all customers.

Prior to this release, after a template or budget entity was forwarded, approved, or final approved, it had to be sent back for any changes. You had to return the template to an In Progress state by sending it back, make revisions, and then forward and approve it once again. This also required higher level user access.

To help users undo their action on a template/entity, we have introduced an option named Recall. Users who perform an action on an artifact can undo their action by using the Recall option.

The Recall option is only available for users who have performed an action on a template/entity until the template/entity has not been moved to the next stage by another user.

For example, let us consider that you have forwarded an HR template and want to recall it to make some changes. You can recall the template until it is not approved by another user. Once the HR template has been approved, you cannot recall it.

In Practice: Recall

1. Go to the Planning Control Panel.

2. Select a scenario, a budget hierarchy entity member, and a template that you have forwarded as shown in the image.

   

3. Click Recall.

   

   The template is moved to an In progress state.

   Note:

   When you Recall an entity, this action is a “smart” undo; because this action truly reverses the action that you previously performed. Consider an example where you selected an entity that has 5 templates within it; template 1, 2, and 3 have been forwarded by another user. If you then Forward the entity, this action will forward the remaining templates (4 and 5). If you perform a Recall action, only the entity and templates 4 and 5 are moved back to an In Progress state. The state of templates 1, 2, and 3 (which were forwarded by another user before you performed the Recall action) will not be changed.
   Note:

   The Recall option is also applicable for approved/final approved entities and for approved templates.

Enhanced Send Back Action for Templates/Entities

This functionality is now enabled by default for all customers.

Prior to this release, after a template or budget entity was sent back, it moved to an In Progress state by default. We have modified this functionality to enable users to send back a template or budget entity to the previous state, and not directly to an In Progress state.

In Practice: Send Back

1. Go to the Planning Control Panel.

2. Select a scenario, a budget hierarchy entity member, and a template that you want to send back as shown in the image.

3. Click Send Back.

   

   The template is sent back to an In Progress state.

   Note:

   The Send Back action is available for approved templates, but not for final approved entities.
   Note:

   The Send Back action is no longer available on the Add Approval Role/Edit Approval Role screen, because it is available to all users with proper privileges.

Availability of Send Back and Recall options for users

This table lists the availability of Send Back and Recall options for users who have the following approval actions for a budget entity.

The following example explains in detail the behavior of both the Recall and Send Back options:

Hierarchy:

List of users with Approval actions:

• Joe has Final Approve permissions for Parent Entity, Entity 1, and Entity 2.

• Jack has Approve permissions for the entire hierarchy.

• Harry has Forward permissions for all the entities and templates; for example, Entity 1 (Template1, Template 2, and Template 3) and Entity 2.

• Tom has Forward permissions for all the entities and templates; for example, Entity 1 (Template1, Template 2, and Template 3) and Entity 2.

  

1. If Tom forwards Template 1, he can view the Recall option for Template 1.

   • Harry can view the Send Back option for Template 1.

   • Jack can view the Approve and Send Back options for Template 1.

   • Joe can view the Approve and Send Back options for Template 1.
     

2. If Harry then forwards Entity 1, Template 2 and Template 3 are also forwarded.

   • Harry can use the Recall option for Entity 1, and this action will move Entity 1, Template 2, and Template 3 to an In Progress state.

   • Harry can also use the Send Back option for Entity 1, Template 1, Template 2, and Template 3; if he wants to move either of these artifacts to an In Progress state and not the entire Entity 1 hierarchy.

   • Tom and Harry can use the Send Back All option for Entity 1. This will send back Entity 1 and all its artifacts (Template 1, Template 2, and Template 3) to an In Progress state.

   • Tom can use the Send Back option for Template 2 and Template 3.

   • Jack can use the Approve, Send Back, and Send Back Alloptions for Entity 1.

     • Jack can move Entity 1 and all its artifacts (Template 1, Template 2, and Template 3) to an Approved state by using the Approve option.

     • Jack can move the Entity 1 to an In Progress state by using the Send Back option.

     • Jack can move Entity 1 and all its artifacts (Template 1, Template 2, and Template 3) to an In Progress state by using the Send Back All option.

   • Jack can also use the Send Back option explicitly for Template 1, Template 2, and Template 3.

   • Joe can use the Final Approve, Approve, Send Back, and Send Back All options for Entity 1. Joe can also use the Send Back option explicitly for Template 1, Template 2, and Template 3.

     

3. Now if Jack approves Entity 1, Entity 1 and all its artifacts (Template 1, Template 2, and Template 3) are moved to an Approved state.

   • Jack can use the Recall option for Entity 1 to move Entity 1 and all its artifacts (Template 1, Template 2, and Template 3) back to a Forwarded state.

   • Jack can use the Send Back All option only for Entity 1. He can also use the Send Back option explicitly for Entity 1 and each of its artifacts (Template 1, Template 2, and Template 3).

   • Joe can use the Final Approve, Approve, Send Back, and Send Back All options for Entity 1. Joe can also use the Send Back option explicitly for Template 1, Template 2, and Template 3.

   • Harry and Tom can only use the Workflow History option in this scenario.

     

4. If Joe then final approves Entity 1, Entity 1 and all its artifacts (Template 1, Template 2, and Template 3) are moved to a Final Approved state.

   • Joe can use the Recall option for Entity 1 to move Entity 1 and all its artifacts (Template 1, Template 2, and Template 3) back to an Approved state.

   • Joe can use the Send Back All option for Entity 1. He can also use the Send Back option explicitly for Entity 1 and each of its artifacts (Template 1, Template 2, and Template 3).

   • Harry, Tom, and Jack can only use the Workflow History option in this scenario.

     

Planning: Ability to Reset a Scenario to In Progress

This functionality is now enabled by default for all customers.

Previously, if Admin users wanted to reset templates and entities (associated with a scenario) to an In Progress state, they had to manually send back each template and entity.

To eliminate clicks and move all the templates and entities associated with a scenario to In Progress at one go, we have introduced the Reset All option. You can use the Reset All option to move a scenario and all its associated templates and entities to an In Progress state, with just a single click.

In Practice: Reset All

1. Go to Maintenance > Admin > Scenario Setup, and then access the Scenario List page.

2. Select the scenario associated with the templates and entities that you want to reset to an In Progress state.

3. Click the More list box, and then select Reset All.

   The scenario and its associated templates and entities are moved to an In Progress state.

Planning: Consistent Display of Current Date and Time

All the fields and columns that used to display UTC date and time earlier, such as Modified Date, Created Date, and Due Date, have been enhanced to display these details according to a user’s current time zone.

The areas in the application that will continue to display UTC date and time are as follows:

• Task Manager: Due Date displayed on the Activity tab

• Task Manager: Due Date change notification

Planning: Plan Scenario Updates

During the Spring 19 release, we had introduced a scenario type called Plan Scenario to enhance the usability and functionality related to creating and interacting with different scenarios.

With the Fall 19 release, Plan Scenario has been enhanced. Plan Scenario is more flexible now, with Notes, Sublines, and Dynamic Journals as optional seeding types. In addition, the process to seed data for closed periods for rows without account mapping has been improved. Also, for custom time sets, an additional functionality has been added to help manage seeding requirements.

The list of improvements made to the Plan Scenario is as follows:

• Notes, Sublines, and Dynamic Journals have been made optional: Earlier, other seeding types such as Notes, Sublines, and Dynamic Journals were selected by default. This feature has now been modified to make the selection of these seeding types as optional. The checkboxes for Notes, Sublines, and Dynamic Journal are cleared by default; you can select the required checkbox and only that data will be seeded to the target scenario.

  

• Data seeding for closed periods: The data seeding process for closed periods for lines (with and without account mapping) has been improved. A section has been added to map the closed periods in a Plan Scenario to the required scenario. You can now seed actual data for closed periods from the required scenario.

  Prior to this release, the data was retrieved based on the data in the source (for the same period), irrespective of the seeding.

  • In the target scenario, for lines without account mapping, the data for closed periods is seeded from the selected reference scenario.

    

  • In the target scenario, for lines with account mapping, the data for closed periods is seeded from the selected source scenario. This will help you to derive actual data for closed periods for lines with account mapping. You can now modify the data in the Source Scenario and Source Period columns on the Closed Period Adjustment tab at any time.

    

  • Note:

    Closed periods data for lines without account mapping is derived from the reference scenario. The reference scenario for these lines cannot be changed, but you can change the source periods for these lines.

• Years tab for custom time sets in templates: To map templates (in reference scenario) with custom time sets to target periods in Plan Scenario, tabs for number of years have been introduced in the Seed Data Form.

  For example, a scenario that has custom time sets defined and has a 5-year template, 3-year template, and a 2-year template. In this case, three tabs with the name 5 Year, 3 Year, and 2 Year are displayed. You can map all the periods in the Plan Scenario by using these tabs. These tabs will also help you to define source periods for different templates with custom time sets and retrieve the data from the required source periods to the target periods.

  

  Note:

  If there are no custom time sets in the reference scenario (source scenario), these year tabs are not displayed.
  Note:

  After you save the source periods, they cannot be changed.

• History columns: Formulas based on History columns are not transposed; instead, History column formulas are copied to the target scenario. The following example explains the adjustment of formulas based on History columns:

  • In the source scenario – Jan 2018 period – row 21, the formula is defined based on the History column in Jan 2017: cell BC21 references cell AE21.

    

  • When this formula is seeded into the target scenario, the position of Jan 2019 changes; but, the formula still refers to the same History column reference: cell AQ21 refers to cell AE21.

    

Planning: Employee Load API Updates

The Employee Load API has been enhanced to process employees automatically when you load multiple employees by using this API. To process all the employees automatically by using this API, on the Configuration Task page, in the Define Detailed HR Budgeting Criteria task, for the Enable Delta Processing list box, you must select the Yes option.

If you choose No for the Enable Delta Processing list box, the uploaded employees will not be processed automatically, and the Auto process stopped as Employee Delta process is not enabled notification is displayed. The Auto Process field is included in the Employee Load API definition.

Sample:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.HostAnalytics.com/API/SOAP/StateFree/Common/2009/03/19">

<soapenv:Header/>

<soapenv:Body>

<ns:LoadEmployees>

<!--Optional:-->

<ns:LoginName>?</ns:LoginName>

<!--Optional:-->

<ns:Password>?</ns:Password>

<!--Optional:-->

<ns:TenantCode>?</ns:TenantCode>

<!--Optional:-->

<ns:employees1>

<!--Zero or more repetitions:-->

<ns:EmployeePosition>

<!--Optional:-->

<ns:EmployeeInfo>

<!--Optional:-->

<ns:ScenarioCode>?</ns:ScenarioCode>

<!--Optional:-->

<ns:HomeBudgetEntityCode>?</ns:HomeBudgetEntityCode>

<!--Optional:-->

<ns:Number>?</ns:Number>

<!--Optional:-->

<ns:Name>?</ns:Name>

<ns:HireDate>?</ns:HireDate>

</ns:EmployeeInfo>

<!--Optional:-->

<ns:PositionName>?</ns:PositionName>

<!--Optional:-->

<ns:PositionEntityCode>?</ns:PositionEntityCode>

<!--Optional:-->

<ns:OtherSegmentCodes>

<!--Zero or more repetitions:-->

<ns:KeyValues>

<!--Optional:-->

<ns:Key>?</ns:Key>

<!--Optional:-->

<ns:Value>?</ns:Value>

</ns:KeyValues>

</ns:OtherSegmentCodes>

<!--Optional:-->

<ns:EmployeeTypeCode>?</ns:EmployeeTypeCode>

<!--Optional:-->

<ns:PayPlanCode>?</ns:PayPlanCode>

<!--Optional:-->

<ns:WageType>?</ns:WageType>

<ns:RateperHour>?</ns:RateperHour>

<ns:WorkHours>?</ns:WorkHours>

<ns:Salary>?</ns:Salary>

<ns:FromDate>?</ns:FromDate>

<ns:TerminationDate>?</ns:TerminationDate>

<!--Optional:-->

<ns:reviewType>?</ns:reviewType>

<ns:NextReviewDate>?</ns:NextReviewDate>

<!--Optional:-->

<ns:Attribute>

<!--Zero or more repetitions:-->

<ns:KeyValues>

<!--Optional:-->

<ns:Key>?</ns:Key>

<!--Optional:-->

<ns:Value>?</ns:Value>

</ns:KeyValues>

</ns:Attribute>

<!--Optional:-->

<ns:CompensationItem>

<!--Zero or more repetitions:-->

<ns:KeyValues>

<!--Optional:-->

<ns:Key>?</ns:Key>

<!--Optional:-->

<ns:Value>?</ns:Value>

</ns:KeyValues>

</ns:CompensationItem>

<ns:BudgetReviewPercentage>?</ns:BudgetReviewPercentage>

<ns:CurrentReviewPercentage>?</ns:CurrentReviewPercentage>

<!--Optional:-->

<ns:BudgetRaiseMultiple>

<!--Zero or more repetitions:-->

<ns:APIBudgetReviews>

<ns:Date>?</ns:Date>

<ns:Percentage>?</ns:Percentage>

</ns:APIBudgetReviews>

</ns:BudgetRaiseMultiple>

<!--Optional:-->

<ns:notes>?</ns:notes>

</ns:EmployeePosition>

</ns:employees1>

<ns:payRollUploadDate>?</ns:payRollUploadDate>

<ns:AutoProcess>?</ns:AutoProcess>

</ns:LoadEmployees>

</soapenv:Body>

</soapenv:Envelope>

Example:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/ [schemas.xmlsoap.org]" xmlns:ns="http://www.HostAnalytics.com/API/SOAP/StateFree/Common/2009/03/19">

<soapenv:Header/>

<soapenv:Body>

<ns:LoadEmployees>

<!--Optional:-->

<ns:LoginName>hchamarthi@hostanalytics.com</ns:LoginName>

<!--Optional:-->

<ns:Password>Wfp@1234</ns:Password>

<!--Optional:-->

<ns:TenantCode>WFPOnetimeGFNew</ns:TenantCode>

<!--Optional:-->

<ns:employees1>

<!--Zero or more repetitions:-->

<ns:EmployeePosition>

<!--Optional:-->

<ns:EmployeeInfo>

<!--Optional:-->

<ns:ScenarioCode>EUB_Budget2018</ns:ScenarioCode>

<!--Optional:-->

<ns:HomeBudgetEntityCode>45</ns:HomeBudgetEntityCode>

<!--Optional:-->

<ns:Number>Host2000</ns:Number>

<!--Optional:-->

<ns:Name>HA2000</ns:Name>

<ns:HireDate>2017-12-12</ns:HireDate>

</ns:EmployeeInfo>

<!--Optional:-->

<ns:PositionName>HA2000</ns:PositionName>

<!--Optional:-->

<ns:PositionEntityCode>leaf</ns:PositionEntityCode>

<!--Optional:-->

<ns:OtherSegmentCodes>

<!--Zero or more repetitions:-->

<ns:KeyValues>

<!--Optional:-->

<ns:Key>?</ns:Key>

<!--Optional:-->

<ns:Value>?</ns:Value>

</ns:KeyValues>

</ns:OtherSegmentCodes>

<!--Optional:-->

<ns:EmployeeTypeCode>basic</ns:EmployeeTypeCode>

<!--Optional:-->

<ns:PayPlanCode>Equal Monthly</ns:PayPlanCode>

<!--Optional:-->

<ns:WageType>S</ns:WageType>

<ns:Salary>108000</ns:Salary>

<ns:FromDate>2018-01-01</ns:FromDate>

<!--Optional:-->

<ns:reviewType>Single</ns:reviewType>

<!--Optional:-->

<ns:notes>?</ns:notes>

</ns:EmployeePosition>

<ns:EmployeePosition>

<!--Optional:-->

<ns:EmployeeInfo>

<!--Optional:-->

<ns:ScenarioCode>EUB_Budget2018</ns:ScenarioCode>

<!--Optional:-->

<ns:HomeBudgetEntityCode>leaf</ns:HomeBudgetEntityCode>

<!--Optional:-->

<ns:Number>HA3000</ns:Number>

<!--Optional:-->

<ns:Name>HA3000</ns:Name>

<ns:HireDate>2017-12-12</ns:HireDate>

</ns:EmployeeInfo>

<!--Optional:-->

<ns:PositionName>HA11</ns:PositionName>

<!--Optional:-->

<ns:PositionEntityCode>leaf</ns:PositionEntityCode>

<!--Optional:-->

<ns:OtherSegmentCodes>

<!--Zero or more repetitions:-->

<ns:KeyValues>

<!--Optional:-->

<ns:Key>?</ns:Key>

<!--Optional:-->

<ns:Value>?</ns:Value>

</ns:KeyValues>

</ns:OtherSegmentCodes>

<!--Optional:-->

<ns:EmployeeTypeCode>basic</ns:EmployeeTypeCode>

<!--Optional:-->

<ns:PayPlanCode>Equal Monthly</ns:PayPlanCode>

<!--Optional:-->

<ns:WageType>S</ns:WageType>

<ns:Salary>108000</ns:Salary>

<ns:FromDate>2018-01-01</ns:FromDate>

<!--Optional:-->

<ns:reviewType>Single</ns:reviewType>

<!--Optional:-->

<ns:notes></ns:notes>

</ns:EmployeePosition>

</ns:employees1>

<ns:payRollUploadDate>2018-10-10</ns:payRollUploadDate>

<ns:AutoProcess>yes</ns:AutoProcess>

</ns:LoadEmployees>

</soapenv:Body>

</soapenv:Envelope>

Success Response:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/ [schemas.xmlsoap.org]" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance [w3.org]" xmlns:xsd="http://www.w3.org/2001/XMLSchema [w3.org]">

<soap:Body>

<LoadEmployeesResponse xmlns="http://www.HostAnalytics.com/API/SOAP/StateFree/Common/2009/03/19">

<LoadEmployeesResult>

<EmployeeStatuses>

<EmployeeStatus>

<EmployeeInfo>

<ScenarioCode>EUB_Budget2018</ScenarioCode>

<HomeBudgetEntityCode>45</HomeBudgetEntityCode>

<Number>Host2000</Number>

<Name>HA2000</Name>

<HireDate>2017-12-12T00:00:00</HireDate>

</EmployeeInfo>

<Status>true</Status>

<ErrorMessage>Employee added successfully.</ErrorMessage>

<PositionName>HA2000</PositionName>

</EmployeeStatus>

<EmployeeStatus>

<EmployeeInfo>

<ScenarioCode>EUB_Budget2018</ScenarioCode>

<HomeBudgetEntityCode>leaf</HomeBudgetEntityCode>

<Number>HA3000</Number>

<Name>HA3000</Name>

<HireDate>2017-12-12T00:00:00</HireDate>

</EmployeeInfo>

<Status>true</Status>

<ErrorMessage>Employee added successfully.</ErrorMessage>

<PositionName>HA11</PositionName>

</EmployeeStatus>

</EmployeeStatuses>

<TotalEmployeesLoaded>2</TotalEmployeesLoaded>

<EmployeeLoadSuccessCount>2</EmployeeLoadSuccessCount>

<EmployeeLoadFailureCount>0</EmployeeLoadFailureCount>

<ProcessStatusMessage>Employee process triggered successfully</ProcessStatusMessage>

</LoadEmployeesResult>

</LoadEmployeesResponse>

</soap:Body>

</soap:Envelope>

Reporting: Enabled Options for Single Dimension Rule in Report Set

The Report Set has been enhanced to include Options for Single Dimension Rule type. Now, all the options that are supported by Dynamic Reports are available in Single Dimension rule.

The selected options in a Report Set are dynamically applied at Dynamic Report run time instead of adding members to Report Set lines one time at the setup. This ensures that any new members added in the hierarchy are pulled dynamically without making any changes to Report Set definitions. This is applicable to Main, Alternate, Attribute, and Attribute Hierarchies, Substitution (Standard and Derived) Variables when used within the Single Dimension rule in a Report Set. Additionally, this is available in all Reporting Areas (Financial, Workforce, Scorecard).

The following fields have been added to the Edit Rule window:

Suppress Indents

A Suppress Indents check box has been introduced. You can select this check box to remove indents from the output for the selected member(s), children, all children, the selected member(s) plus the children, the selected member(s) plus all children, leaves, the selected member(s) plus leaves, or the selected member(s) plus the parents.

Options

Options drop-down list has been added to the Edit Rule window. The drop-down list is enabled only when a single rollup member is selected in the rule. The following options are available in the drop-down list:

• Selected (default) - Members in the tree, as selected by the user:

• Children - Immediate children of members, as selected by the user

• Selected + Children - Selected members, and their immediate children

• Selected + All Children - Selected members, and all levels of children under them

• Leaves - Leaf members at all levels under the selected members

• Selected + Leaves - Selected members, and their leaf members, at all levels

• Selected + Parents - Selected members, and their immediate parents

The following additional options are available for the Time dimension:

• Year

• Quarter

• Month

• Trailing

• Total - Trailing

The default value is Selected in the Options drop-down list for all the existing and new Report Sets. This is available across all Reporting Areas in both the Classic and Modern Report Sets.

Display Parents Last

A Display Parents Last check box is available for the Selected + Children, Selected + All Children, Selected + Leaves, and Selected + Parents options. If the check box is selected, the parent member will be displayed at the bottom of the hierarchy.

The following image displays the fields added to the Edit Rule window.

The Excel Formulas, Insert Formulas, Formula exceptions are automatically adjusted when Options are dynamically applied at Dynamic Report run time.

The selected Options is displayed in the Report Set based Dynamic Report as shown in the image below.

Limitations

• When you copy and paste a rule line using the keyboard, the selected Options is not retained. If you edit the rule, the Edit Rule window opens in the Advanced tab.

• When you define Excel formula on a rule, the member is displayed in Dynamic Reports only when you select Selected + Children, Selected + All Children, Selected + Leaves and Selected + Parents from the Options drop-down list.

• When you add a conditional format on a line with reference to another line, the Report Set rule with the following Options is not supported:

  • Children

  • All Children

  • Leaves

  • Year

  • Quarter

  • Month

  • Trailing

  • Total - Trailing

Reporting: Configurable Time Dimension

With this release, Calendar Start Year configured in the Define Fiscal year Setup page will be displayed across the Time dimension fields. Now, you can edit the Calendar Start Year field in the Define Fiscal year Setup page based on your requirement.

In Practice: How to change Calendar Start Year

To change Calendar Start Year:

1. Navigate to Maintenance > Admin > Configuration Tasks.

2. Click Define Fiscal year.

3. Select the required start year from the Calendar Start Year drop-down list.
   

The Time dimension used in the Members section and dimension control fields across Reporting (including Standard Reports), and Dashboards are updated based on the start and end year as configured for the application in the Define Fiscal year Setup page. Also, all the reports data will be displayed based on the selected start year.

If a member is used in the following fields prior to the selected start year:

• Page axis- The default member value is used to run the report.

• Row and Column axis- You need to update the member value to run the report.

• Report Collection- The default member value is used to run the report.

Reporting: Dynamic Report Output Usability

The format and style of the Dynamic Report output have been enhanced for better user experience. The following enhancement has been made:

• The font format and size of the following fields have been enhanced:

  • Formula Bar

  • Report Title

  • Grid Headers

  • Grid cells

  • Header and Footer section

  • Drill Through data

    Also, the grid alignment, freeze pane, and scroll bar have been enhanced for usability. The format and styling are retained in the drill down report.

• A pop-up window has been added to the Status bar. Right click on the status bar to open the window and select the required fields that you want to display. The following image displays the pop-up window and styling added to the Dynamic Report output.

  

The font size of Insert Format, Header, and Footer is retained when you save a report. The font size is not altered even if you enable or disable the functionality.

When functionality is enabled, re-arranging the sequence of Header and Footers will not change the font family and size of the first row of header.

Reporting: Report Sets Usability

The following enhancements have been made to both the Classic and Modern Report Sets:

Show/Hide/Re-arrange Columns

A Show/Hide/Re-arrange Columns settings icon has been added to the toolbar. Now, you can show, hide, and re-arrange the columns based on your requirements. You can drag and drop a column to reorder in the Show/Hide/Re-arrange Columns drop-down window. The column settings are retained when you access the Report Set next time and export a Report Set to excel.

Format Painter

A Format Painter icon has been added to the toolbar. You can copy the format of a cell and paste the format to other cells. The text and data format is copied from the source cell to the target cell.

You can copy the format and paste to all cells, Report Set lines including row, column headers, merged lines, excel formulas. The data format can be copied and pasted to the Report Set line only. The format is retained when you Save, Run, Refresh, Save As, Copy, and export a Report Set.

Additionally, this options are available in all Reporting Areas (Financial, Workforce, Scorecard).

Reporting: Dynamic Reports Headers

With this release, when a Static or Dynamic Report Set is used on the row axis of a Dynamic Report, the primary dimension which is used in the Report Set is reflected as the column header in the report. This is also applicable to Dynamic Report Set used in combination with other Report Sets and dimensions.

For example, if you use Account dimension to create a Report Set and then select the Report Set on the Row axis of a Dynamic Report then Account is displayed as the column header. The following image displays the Dynamic Report with Account as the column header.

Reporting: Consistent Display of Current Date and Time

All the fields and columns that display date and time, such as Modified Date, Created Date, and Due Date, have been enhanced to display these details according to a user’s current time zone.

With this release, the following areas in the application will display date and time according to a user’s current time zone:

• Drill Through - Transaction Date Attributes

• Template Notes

The areas in the application that will continue to display UTC date and time are as follows:

• Standard Reports including Template Notes

• Dynamic Reports - Dimensions (in Scorecard and Workforce Reporting Area), Attributes, Attributes Hierarchies, properties as dates.

• When you export a file from the application, the date and time format is displayed as text.

Reporting: Code, Name, and Label Display Consistency

With this release, Code, Name, and Label display configuration are made consistent for the header, footer, and member selections across all the Reporting areas. The default value is Label.

Prior to this release, Code, Name, and Label display was disabled when the Scenario dimension is added to the Page axis of a Dynamic Report.

When the Show Pick List check box is selected for a dimension added to the Page axis and you run the Dynamic Report; Code, Name, and Label display is retained for the members displayed in the pick list.

Code, Name, and Label display set up for a dimension within the Dynamic Report member selections is retained when you view the drill through metadata. If Display Currency configuration is enabled in the application for Reporting dimensions, LC and CC values are replaced with the appropriate currencies in the drill through metadata.

Reporting: Drill Through Icon in Dynamic Reports

A Drill Through icon is added to the Dynamic Reports toolbar. Now, you can view the drill through report by clicking the icon.

The icon is visible in the toolbar across all Dynamic Reports on Financial reporting area where Drill Through is enabled in the report. Additionally, the icon is enabled only for those cells where drill through is applicable. It is disabled for header, excel, row title, Insert Formula, formula exception, and advanced formula cells.

You can view the drill through report in the following ways:

• Click the Drill Through icon

• Double click the cell on the grid

Reporting: IDX Column in Segment Hierarchy Standard Report

With this release, we have introduced a column IDX (Index number) in the Standard Report for all Segment Hierarchy. The IDX columns display the Index number associated with the member. You can use the IDX number in the Standard Report to create formulas in the report.

Previously, IDX for a member was displayed only in the Hierarchy Selection page. Only the users who have access to the Hierarchy Selection page could view the IDX number.

Reporting/Modeling: Grouping Functionality in Spotlight Web Reports

Rows and columns can be grouped and saved for a report from SpotlightXL. Multiple groupings can be defined for a single report. When the reports defined in SpotlightXL are accessed from Spotlight (web version), the grouping defined on the report in SpotlightXL is retained. This functionality is available for all reports created for any models.

In Practice

1. Access SpotlightXL.

2. Access a report (Report > Run) that you want to add a group to.

3. Select Design (under Run).

4. Highlight the rows or columns you want to group as shown below.

   

5. Click the Data tab and select Group.

   

6. Return to the SpotlightXL tab.

7. Save the report.

8. Run the report. Notice the grouping is applied.

   

9. Login to Spotlight. When you run the same report, the grouping is applied.

   

Reporting/Modeling: Grouping in Cascade Reports

Host currently supports the grouping of rows and columns in SpotlightXL/Spotlight Reports. With this release we support Cascade Reporting row and column groupings; as long as the groupings are defined within the Cascade Block. The Cascade Block is comprised of the row which starts with a cascaded dimension to the ending innermost dimension member. For example, cell B3 through cell F23.

Let’s say you’ve design the following Cascade Report.

When you run the report, the output will look as follows in the image below.

If you save with the report with the groups collapsed or expanded, the Cascade Report will save along with the report definition. When you refresh, the group will either be expanded or collapsed based on what you define during report design.

Here is an example with a groups expanded design:

Here is an example with a groups collapsed design:

In Practice: Grouping Rows in SpotlightXL

1. Select the rows you want to group.

2. Click the Data tab.

3. Click the Group option.

4. Return to the SpotlightXL tab.

   

In Practice: Ungrouping Rows in SpotlightXL

1. Select the rows you want to ungroup.

2. Click the Data tab.

3. Click the Ungroup option.

4. Return to the SpotlightXL tab.

See Also: Cascade Reporting

This feature does not work when you have a 1 row cascade report design as shown below.

Reporting/Modeling: Ability to Close All Other Tabs in Spotlight Views and Reports

Now you can close all other tabs except for the one that is active in Spotlight views and reports at once.

In Practice: Closing Other Tabs in Views

1. Open several tabs in Spotlight.

2. Open a view by navigating to Analyze > Data and selecting a view.

3. Click the ribbon at the bottom on the screen (as shown below) and click Close Other Tabs.

   

In Practice: Closing Other Tabs in Reports

1. Open several tabs in Spotlight.

2. Open a report by navigating to Report > Run and selecting a report.

3. Click the ribbon at the bottom on the screen (as shown below) and click Close Other Tabs.

   

Reporting/Modeling: Multiple POV Selections in SpotlightXL and Spotlight for Direct Connect Models

With this release you can select multiple members of page filters for views and reports built on Direct Connect Models. A Direct Connect model is one created with Direct Access to PCR enabled.

For detailed information on Direct Connect models, click here.

This feature is enabled for all main, alternate, attribute and attribute hierarchies added to page filters.

In Practice: Selecting Multiple Members in a View in SpotlightXL

1. Open a view (Analyze > Data > Select the View).

2. Select the drop-down for a page filter. In this example it is the Department dimension.

3. Select all dimension members you want displayed by selecting the checkbox next to each. In this example, FIX and TAX are selected.

   

   Note:

   While selecting multiple members from the dimension browser drop-down, you have to select the required dimension members and click Select.

4. The selected members are displayed as comma separated values (as shown in the image below).

   

If you decide to move the dimensions from the page to a row or column, the dimension tree is updated intuitively to display the dimensions.

Once you move the dimensions selected from the page to a row or column, you can save the view as a report and run it.

In Practice: Selecting Multiple Members in a View in Spotlight

Here is a page shot from Spotlight (web version) showing the ability to select multiple members for the Product Main dimension.

In Practice: Selecting Multiple Members in a Report in SpotlightXL/Spotlight

1. Open a report (Report> Run).

2. Select the drop-down for a page filter.

3. Select all dimension members you want displayed by selecting the checkbox next to each.

Reporting/Modeling: Support for Drill Through in Direct Connect Models in Both SpotlightXL and Spotlight

Decision making is even easier with Direct Connect Model Drill Through functionality, which is available in SpotlightXL and Spotlight (web interface). Drill through a Direct Connect model report to retrieve the following source data:

• Transactions

• Translations

• Operational Planning data

• Planning data in shared mode enabled applications

• Seeding (preloaded) data for Preloaded & Forecast scenarios

• Closed Periods data for Forecast scenarios

• Capital and Workforce Planning data

• Consolidation data

• GL data loaded via Data Load Rules

For information on how to create a Direct Connect Model, click here.

Drill through is enabled in your reports for a data cell where dimensions, attributes, attribute hierarchies, main hierarchy, alternate hierarchies and substitution variables are used. However, drill through is not supported if multiple Scenarios or multiple members on any other dimensions are selected on the page filters (the ability to select multiple scenarios on the page filter is available with this release). All drill through reports honor Dimension Security with the exception of Workforce drill through data, which additionally honors Budget Entity and Template Access by default.

Reporting/Modeling: Drill Through Grid Interaction in Spotlight

Now, when you perform a drill through from a model view, you can interact with the resulting Drill Through report in the following ways:

• Drag and drop a single column, a range of columns, or multiple columns to reorder them

• Adjust the width of a single column, a range of columns, or multiple columns

• Sort column data in ascending or descending order

• Select the code, name and label display for members

In Practice:

1. Open a view by navigating to Analyze > Data and selecting a view.

2. Click the Drill Through icon as shown below. The Drill Through report is displayed.

   

   

3. Select a column or columns to reorder and drag and drop as shown in the image below.

   

4. Sort the column in ascending or descending order.

   

5. If you change Turn On/Off Settings in the Reporting module, for example, and save then the setting is retained when accessed via Spotlight. You cannot change or save the Turn On/Off setting from Spotlight.

   

6. Display dimension members by code, name or label (the default is set to label which is name+code). If you change the default to code in the Reporting module, for example, and save then the setting is retained when accessed via Spotlight. You cannot save the setting from Spotlight.

   

7. Adjust column width as needed.

   

8. Select to display or hide specific columns.

   

For information on Doc Ref, Lines, and Sublines, see Dynamic Reports: Enhanced Drilling on Dynamic Report Output

Important Details:

• Data is displayed in the same currency and formatted as loaded or upon input into the application for QTD and YTD or multi-currency calculations in Drill Through reports,

• Subline amounts are stored in local currency and currency conversions do not exist.

• Calculated members, calculations, and Excel formulas, are not supported in Drill Through reports.

• All template types are supported except for Template based HR, Actual Data Template, and Initiative templates.

• Drill Through is not supported with Multiple POV on a cell.

• Export to Excel and saving of User Settings on drill through report are currently not supported from Spotlight.

Reporting/Modeling: SpotlightXL User Experience Improvements in Views

For an improved user experience, we’ve updated the SpotlightXL ribbon when running and designing a view by including frequently used View properties under the More listbox. This prevents the need to go to the Properties screen to define them.

• Change member display from code to label and vice versa

• Change the number format

• Suppress rows

• Suppress columns

• Indent row members

Change Member Display

Open a view and click the More listbox. Select Display.

For information on running and designing a view, click here.

For information on number format, decimal, width, suppress rows and columns, indent row members and show or hide hidden members, click here.

Change the Number Format

Change the number format for numeric values in the displayed view to Currency or Percentage. Numeric is the default.

Suppress Rows/Columns

Suppress no rows/columns (None), suppress rows/columns that have a zero value (Zero), suppress rows/columns that have no data (Blank), or suppress rows/columns that have a zero value and no data (Zero and Blank) for a displayed view.

Indent Row Members

Indent dimension members on the rows for the displayed view. Select On to indent or Off. Off is the default.

Commonly used View Properties are also available in Design View under the More listbox. All the other properties are available in the Properties sheet. See the screenshots below.

Dashboard: Enabled Export for All Browsers

With this release, we have enabled the Export option for all browsers. The Export option is available in the More options drop-down list as shown in the image below.

Prior to this release, the Export option was enabled only for the Google Chrome browser.

Limitations

• When you export any Dashboard:

  • The dimension member label may not be displayed accurately. The workaround is to increase the chart size.

  • The space above the chart filter name gets reduced.

  • The complete filter name is not displayed. The workaround is to increase the chart size.

  • Table borders are not displayed properly.

The above limitations may not occur every time you export any Dashboard.

Best Practice

• If the rendering of the exported dashboard is an important requirement, utilize the export while building the dashboard and adjust the dimensions of the various objects on the dashboard to achieve the most accurate export.

• You need to zoom the exported file for better visibility.

Modeling: New Add-Ins for SpotlightXL and SpotlightXL/Spotlight for Office Available

Please access the Install (SpotlightXL and Spotlight for Office Installation) guide for information to upgrade your existing client software.

Modeling: Calculation Status API Updates

The Calculation Status API returns the current and last status of the running of a calculation. Now, the following fields are included in the Calculation Status API definition:

• Description

• Run in Background

• Last Run Time

POST modeling/model/calcscript/status HTTP/1.1

Content-Type: application/xml

Accept: application/xml

X-ACCESS-TOKEN:

Request body:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<run-calcscript-payload>

<model-name>BOA_Model</model-name>

<calcscript-name>BOA_Model</calcscript-name>

</run-calcscript-payload>

Response body:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<calcscript-status>

<model-name>BOA_Model</model-name>

<calcscript-name>BOA_Model</calcscript-name>

<status>not running</status>

<last-status>success</last-status>

<description></description>

<run-in-background>Yes</run-in-background>

<last-run-time>2019-05-15T10:37:56.036Z</last-run-time>

</calcscript-status>

Compare the Response body above with the legacy below:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<calcscript-status>

<model-name>BOA_Model</model-name>

<calcscript-name>BOA_Model</calcscript-name>

<status>not running</status>

<last-status>success</last-status>

</calcscript-status>

Consolidation: Ability to Export the Security Report

The Consolidation Security Report can now be exported and downloaded. The Consolidation Security Report provides information by user on access to Consolidation Processes.

In Practice

1. Access the Consolidation Control Panel.

2. Under Administration, click Security.

   

3. Click the Export icon (shown below) to export the report displayed on the screen.

   

Consolidation: Ability to Delete Many Dynamic Journal and Non Controlling Interest Lines at Once

With the Summer19 release we provided you with functionality to delete many Standard Journal lines at once. Now, you can do the same with Dynamic Journals and Non Controlling Interest lines; saving time and adding convenience.

In Practice: Deleting Several Non Controlling Interest Lines at Once

1. In the Consolidation Control Panel, select the Non Controlling Interest process. All Non Controlling Interest rows are displayed in the center pane.

2. Open a Non Controlling Interest row.

3. Click the Investment tab.

4. Click the checkbox in the column header to select all Non Controlling Interest lines.

5. Click the Delete icon.

   

Platform: Unified User Management

With this release, you can now access all the Host Analytics modules using one URL. You can access the Spotlight, Modeling, Planning, Consolidation, and Reporting modules through a common URL.

Prior to this release, a separate URL was used to access the Spotlight and Modeling modules.

Once you are unified with the Planning application:

• You can create a new password using the system generated email that will be sent to you.

• You will have only three attempts to log in with the Modeling URL.

• You cannot log in using the Modeling URL, after you login through the Planning URL.

• The security setup configured in the Security Administration page will be applicable to the Modeling user.

With this release, the following fields have been added to the Add and Edit User page:

• Modeling User- Select Yes if you are adding a Modeling user. The Modeling Role drop-down list will be displayed.

• Modeling Role- Select any of the following role based on your requirement:

  • Designer

  • Admin

  • Reviewer

The image below displays the fields added to the Add and Edit User page.

In Practice: How to access the Add and Edit User page

Access the Add User page by navigating to Maintenance > Admin > User Management and click the Add icon. The Add User page appears.

If you want to edit existing navigating to Maintenance > Admin > User Management and select the user that you want to edit. The Edit User page appears.

Platform: Configurable Time Dimension

With this release, Calendar Start Year configured in the Define Fiscal year Setup page will be displayed across all the Time dimension fields. Now, you can edit the Calendar Start Year field in the Define Fiscal year Setup window based on your requirement.

In Practice: How to change the Calendar Start Year

To change the Calendar Start Year:

1. Navigate to Maintenance > Admin > Configuration Tasks.

2. Click Define Fiscal year.

3. Select the required start year from the Calendar Start Year drop-down list.

   

Platform: Consistent Display of Current Date and Time

All the fields and columns that used to display UTC date and time earlier, such as Modified Date, Created Date, and Due Date, have been enhanced to display these details according to a user’s current time zone.

Platform: Enhanced Security by Restricting Emails to Inactive Users

With this release, we have enhanced the application's security by restricting system generated emails to the Inactive user. Even if an inactive user’s email ID is mentioned in a few fields, such as distribution list, the email will not be sent to the users.

Platform: Enhanced Audit Log for Exchange Rates

We have enhanced the format of Audit Log for the Exchange Rates changes. Now, the Audit Description has been updated to display detailed information about the changes made in the Exchange Rates page. The existing values are displayed in the Old Value column and the updated changes are displayed in the New Value column as shown in the image below.

Platform: Heads Up! Windows 7 will not be supported after January 2020

Platform: Employee Processing from DLR

With this release, we have added a Process Employees check box in the Define Overall Rule Settings step. The check box provides you the option to process employees using DLR. The image below displays the check box.

If the Process Employees check box is selected and data is loaded successfully using DLR, then a request to process all the employees will be submitted. The default value is No. For the existing DLRs, this check box will not be selected.

The Process Employees check box is available for the following DLRs:

• Detailed HR - Employee Data

• Detailed HR - Employee Compensation Item

• Detailed HR - Employee Allocations

Platform: Enhanced Audit Log for Translation Lines Setup

We have enhanced the format of Audit Log for the Translation Lines Setup changes. Now, the Audit Description is displayed in separate rows for the Select Source Segments, Select Target Segments, and header section. The existing values are displayed in the Old Value column and the updated changes are displayed in the New Value column as shown in the image below.

If you delete a Translation setup, then the Old and New Value columns will not be displayed.

Platform: Enhanced Account Segment Hierarchy Loads for Flow Dimension Enabled Tenant

With this release, we have enhanced Account Segment Hierarchy Loads to support the FX Currency Type and CTA Account parameters. These two parameters are available in the Define Overall Rule Settings as shown in the image below.

These parameters can be loaded from the file by mapping in the Define Data Mappings step.

Prior to this release, the FX Currency Type and CTA Account parameters were not available in the Define Overall Rule Setting and Define Data Mappings step.

Platform: Name Change from RESTlet URL to External URL in NetSuite Connect

With this release, the RESTlet URL label is changed to External URL in the Configure Profile page of NetSuite Connect.

Platform: Update Bundle for SuiteScript in NetSuite Connect

With the Fall19 release, you need to install the updated bundle for SuiteScript in NetSuite. Follow the steps specified in the next sections to uninstall the old version and install the latest one.

Uninstalling Bundle

To uninstall the Host Analytics NetSuite Connect bundle in Netsuite, follow the steps:

1. Navigate to the Installed Bundles page.

2. In the search field, type Host Analytics NetSuite Connect. The search result is displayed.

3. Click the drop-down icon beside the Host Analytics NetSuite Connect bundle and select Uninstall as displayed in the image below.

   

Installing Bundle

Follow the steps below to install the Host Analytics NetSuite Connect updated bundle:

1. In the Installed Bundles page, navigate to Customization > SuiteBundler > Search & Install Bundles.

   The Search & Install Bundles page is displayed.

2. In the KEYWORDS field, type Host Analytics NetSuite Connect. The search result is displayed as shown in the image below.

   

3. Click Host Analytics NetSuite Connect. The Bundle Details page is displayed.

4. Click Install as shown in the image below.

   The Preview Bundle Install page is displayed.

5. Click Install Bundle as shown in the image below.

   A confirmation message will be displayed.

6. After the installation is complete, type Host_ NetSuiteConnect in the search filed of the Installed Bundles page. Select Page: Host_NetSuiteConnect as shown in the image below.

   The Script Deployment page is displayed.

7. In the FILTERS section, select All from the drop-down box.

   

8. Click View.

   

   Note:

   Copy the EXTERNAL URL and use the URL while setting up NetSuite Connect in Host Application.
   Note:

   Replace the existing EXTERNAL URL in the NetSuite Connect Profile with the EXTERNAL URL displayed after installation and save the profile.