The BMC Helix Innovation Suite product is now renamed to BMC Helix Platform. To view the latest documentation, see BMC Helix Platform.

If you have bookmarked these pages, you should update them with the new links.

18.11 enhancements

This section contains information about enhancements in version 18.11 of BMC Helix Innovation Suite.

BMC Helix Innovation Suite platform enhancements

BMC Helix Innovation Studio Foundation library enhancements to increase parity with Remedy IT Service Management Suite

The Foundation data model has changed to reduce the restrictions on Organization and Person data so that customers have more control on their data. Customers can now perform the following tasks that were earlier restricted:

  • Transition of data semantics between Remedy IT Service Management (Remedy ITSM) Suite and BMC Helix Innovation Suite. 
  • Convert between types of Organization and Person. 
  • Create multiple types for organizations.
  • Leverage recursion for regions and support groups.

Organization data model changes

The hierarchy in Primary organization is no longer applicable. In BMC Helix Innovation Suite version 18.08 and earlier, Primary organization was defined as one of these types: Service Provider, Operating organization, Vendor organization, or Manufacturer. You do not need to create separate record definitions for Primary Organization data and its types, such as Service Provider, Operating organization, Vendor organization, and Manufacturer. The types of Primary Organization are now stored as the Type field in a single Primary Organization record definition.

The Secondary organization data model remains unchanged.

For more information, see Organization data.

The following image represents the changes in the Primary organization:

Person data model changes

The hierarchy for Person data is no longer applicable. In BMC Helix Innovation Suite version 18.08 and earlier, Person data and its types, such as Employee, Agent, Customer, or Vendor were stored as separate record definitions.

Starting from this release, you do not need to create separate record definitions for Person data and its types. The types of Person are now stored as the Type field in a single Person record definition. 

The following image represents the changes for Person data:

For more information, see Person data.

Filtering Foundation data by domain

Developers can leverage domain data tags to filter Foundation data. Filtering of Foundation data by using domain data tag allows you to skip unwanted data, control visibility, and filter Foundation data within your applications.

For example, in your HR services application, you can apply HR domain tag to HR support groups, incident requests, or support tickets to retrieve and show data related to HR only.

For more information, see Filtering Foundation data by domain.

Enhancement to process variable with Document definition support

Developers can access attributes such as, complex objects, array of objects, array of strings, and nested complex objects by using a Document definition. Developers can define document definition when communicating with a third-party module by using custom actions or connectors. The document definition enables you to access the attributes returned by the custom actions or connectors and use these attributes as an input or output within a process.

For more information, see Defining document definitions.

Ability to test the BMC Helix Innovation Studio Cognitive Service data sets and chatbot applications

Administrators can test the BMC Helix Innovation Studio Cognitive Service data sets and chatbot application for accuracy, precision, recall, and F-score. These tests are particularly important when you are implementing a new training data set or if you have made major changes to the data sets. 

Testing the Cognitive Service and chatbot has the following benefits:

  • Helps ensure that the cognitive service selects the correct category with the desired frequency.
  • Helps ensure that the chatbot correctly identifies the intent and responds to the end users accordingly.
  • Helps identify the exact problem area so that you can rectify the data sets to improve the performance of the cognitive service.
  • Provides a history of the test results. 

For more information, see Leveraging machine learning metrics to improve cognitive service data sets.

Connect to RESTful services without using code

Developers can connect to RESTful services in a codeless way by using the BMC Helix Innovation Studio UI. This eliminates the need to install an IDE, write Java code, or run and manage an Integration Controller. You define a one-time configuration for each RESTful service, and create a business process for various HTTP methods such as GET, PUT, POST, or DELETE. 

For example, by using this feature, you can connect to JIRA RESTful service in a codeless way to get details of a JIRA issue or update the JIRA issue. For more information, see Integrating with REST services in a codeless way.

Application development enhancements

Email enhancements

BMC Helix Innovation Studio enhances the email capabilities by providing the following features:

  •  Administrators can now restrict the total number of attachments and the total size of the attachments that can be added to an outgoing email. For more information, see Updating centralized tenant configuration settings.
  • Administrators can now configure outgoing profiles to update the outgoing mailbox without the need to modify the existing processes and rules.
    For example, consider a scenario where you use outgoing mailbox in multiple processes and rules to send email notifications to the employees of Calbro Services.
    Calbro Services organization now wants to seperate HR emails based on locations (India and US). As a result, the processes and rules will need to be updated manually for two different outgoing mailboxes. 

    With this enhancement, an administrator can now map the outgoing mailbox to an outgoing email profile and use this profile in the processes and rules. So that even after you update the outgoing mailbox, the processes and rules remain unaffected and continue to send email notifications by using correct outgoing mailbox.

    For more information, see Configuring incoming and outgoing email

Approval enhancements

The Approval application now supports the following two enhancements:

  • Cancellation of user-driven approval requests that are in pending state. For more information, see Creating an approval process.
  • In general approval flows, while selecting approvers, users can now filter approvers from the foundation data. Users can apply filters to the functional roles, business units, support groups, person, location, and so on. This helps in narrowing your selection to an approver belonging to a business unit or functional role, instead of the whole business unit or functional role.
    For more information, see Configuring approval flows.

BMC Helix Innovation Suite Interface design enhancements

Ability to change the layout of view components

Developers can now change the layout of view components and improve the clarity and readability of the information that is displayed on the application.

You can choose from the following layouts:

  • Display the Boolean view component as a check box or as a switch.
  • Display the Select view component as radio buttons or as a list.

For example, in an ServiceDesk application, that users can use to create helpdesk tickets, you can configure the layout of view components as follows:

  • Status record field such that the options are displayed as radio buttons
  • Does this issue impact the team? Boolean field such that it is displayed as a check box
  • Time to Resolve record field such that the options are displayed in a list
Example of view configuration Example of view display

For information about how to choose the layout of view components, see Creating a view for a record instance using Record Editor.

Grid enhancements

The Record Grid component supports the following enhancements:

  • Developers can enable editing of multiple records in a record grid by using the Edit Records action. For more information, see Configuring actions by using an action button.

  • Developers can now define filter presets that can be used in the deployed application. These filter presets are saved in the view definition and are visible in the deployed application. The users can create their own filter presets. They can either modify a shared filter preset by adding, removing, or editing the filters included in the preset. Users can also define multiple filters and save them as a private preset. The private presets are stored in user preferences. For more information, see Working with the Record Grid.

  • Users can also filter rows by cell selection. The record grid takes the value of the column from the selected row and filters the rows on that value. This displays all the rows with the selected column value. You can select multiple rows and get a list of distinct column values from the selected rows and filters the data by multiple values. For example, Status = "Open" or Status = "In Progress" or Status = "Blocked". If there are more than ten distinct values detected, an error is displayed. 

    Example of filtering rows by cell selection


Support for customizing user menu to display the user profile

By using BMC Modern Shell, application business analysts and developers can now customize the user menu to display information about the user's profile. BMC Modern Shell is a built-in landing page and default menu system that is configured for every application. You can provide information about the user and the application settings for that user, and display it on the application menu.

The following image is an example of a View Profile menu item that is added to the user menu:

For information about how to customize the user menu, see To customize user menu.

Responsive web layout

BMC Helix Innovation Suite views are rendered with a responsive layout in browsers. In responsive layouts, the components wrap vertically when the width of the browser's viewport is not sufficient to display them as laid out in the View designer. This feature is useful in the mobile device browsers such as smart phones, tablets, and so on. You can also simulate the layouts on various devices. You can control the layout size by configuring the Row Wrap property in the Container view component and the modal views in the Open View actions.

 For more information on responsive web layout, see Creating a responsive web layout.

Related topics

Limitations and upgrade considerations

Known and corrected issues

Was this page helpful? Yes No Submitting... Thank you