BMC Helix Platform 20.08

BMC Helix Platform is a combination of services and components that helps you develop, build, deploy, and use multi-tenant applications on cloud. It also helps you to create and automate many business processes without learning a programming language or complex development tools.

Release notes and notices Updated 08 Feb 2024

Learn what’s new or changed for BMC Helix Platform 20.08, including new features, urgent issues, documentation updates, and fixes or patches.

Tip

To stay informed of changes to this list, click the icon on the top of this page.

Related topics

Known and corrected issues

Deprecated features and post upgrade behavior

FAQs

BMC Helix Chatbot release notes

BMC Helix Business Workflows release notes

The following updates have been added since the release of the space:

Date	Summary	Title
February 6, 2024	Issues that were corrected by 20.08 patch 16 and issues that remain open	20-08-patches
March 6, 2023¹	Issues that were corrected by 20.08 patch 15 and issues that remain open	20-08-patches
June 13, 2022	Issues that were corrected by 20.08 patch 13 and issues that remain open	20.08 patches
January 7, 2022¹	Issues that were corrected by 20.08 patch 12 and issues that remain open	20.08 patches
September 16, 2021	Issues that were corrected by 20.08 patch 9 and issues that remain open	20.08 patches
August 23, 2021	Issues that were corrected by 20.08 patch 5 and issues that remain open	20.08 patches
July 28, 2021	Issues that were corrected by 20.08 patch 4 and issues that remain open	20.08 patches
December 16, 2020	Issues that were corrected by 20.08 patch 1 and issues that remain open Updates available in 20.08 patch 1: Support for IBM Watson Plus and IBM Watson Premium plan. Ability to use special characters while logging in to BMC Helix Innovation Studio. Use the Ctrl+click action to open the view in record grid values in a new tab.	20.08 patches
September 23, 2020	BMC Helix Platform has been enhanced in the following areas: Launch codeless applications in the new user interface Run developer sandboxes on your local machine by using a docker container Use your IBM Watson services to leverage BMC Helix Cognitive Automation Foundation data improvements to set the default support group for an agent Cognitive search and chatbot unique user reports available on the UI Create filter presets on UI that is locked for customization Enable and download server logs from BMC Helix Innovation Studio Support for webhook definitions registered with DocuSign Support for Danish and Norwegian languages Set allowed or disallowed attachment types Export and import custom record data between environments Display image from an attachment and enable rich text editing for application users	20.08
May 19, 2020	This update includes fixes for defects and an updated BMC Helix Platform SDK.	Patch 1 for 20.02
February 21, 2020	BMC Helix Platform has been enhanced in the following areas: Early access preview of the Angular framework for BMC Helix Platform Improved cognitive search crawler to include articles from Remedy Knowledge Management Supported Foundation name changes in Remedy IT Service Management Filter a record grid by using partial text strings Set grid filter presets by using partial text strings BMC Helix Chatbot service consumption has been changed from conversation-based to user-based. BMC Helix Cognitive Automation now include Summarization, IBM Watson Assistant Tone Analyzer, and Real Time Translation Support for join on external records Support to set preferred user or global locale Enhanced Extension Container view component to support fields from the same record definition Support for Date and String functions in Expression Editor	20.02
November 22, 2019	BMC Helix Platform has been enhanced in the following areas: Download or upload different types of attachments via a Web API call Use a query as an action to fetch data Support for Automation Anywhere Robotic Process Automation (RPA) Support for adding an array node in a document instance Send and receive attachment and text lists from a process Real-time translation for applications Ability to set the region for IBM Watson services Support for IBM Watson Tone Analyzer service Webhook registration retries to avoid data loss Update Remedy IT Service Management (Remedy ITSM) associations in BMC Helix Platform	19.11
October 10, 2019	This update includes fixes for defects and updated BMC Helix Platform SDK.	Patch 01 for 19.08
August 22, 2019	BMC Helix Platform has been enhanced in the following areas: Support for BMC Native classification for cognitive service Support for webhook definitions registered with Adobe Sign Enable users to directly view an event that triggers a notification Dynamically define the type of association Enhancing the cognitive insights capabilities by providing the following features: Filtering the search data sets by using confidence threshold Ability to rate the most relevant knowledge articles Simplified construction of text strings in an expression builder Content packages for applying customizations to an application	19.08
July, 2019	This update includes fixes for defects and updated BMC Helix Platform SDK.	Patch 01 for 19.05
May 31, 2019	BMC Helix Platform has been enhanced in the following areas: Leverage Remedy Smart Reporting capabilities to generate application usage reports. Support for cognitive search user metrics. Ability to launch the Process designer from a custom application view. Support for cognitive search in custom applications and BMC products. Unique record IDs for Foundation data. BMC Helix Innovation Studio configuration change history. Leverage external AR System data as local data. The Record Grid Component adapts automatically to mobile form factors. A new Tab Panel View Component has been added, which helps you to organize page content within multiple tabs.	19.05
April 17, 2019	This update includes updated BMC Helix Platform SDK and fixes for defects.	Patch 01 for 19.02
February 22, 2019	BMC Helix Platform has been enhanced in the following areas: Integrating applications by using the Webhook definition. Tracking application events to derive application usage metrics. Enhancing the approval capabilities by providing the following features: Configuring the approval flows to allow certain number of approvers to approve the request. Flexibility to plugin any other notification mechanism. Approving or rejecting the requests through email notifications.	19.02
December 19, 2018	This update includes updated BMC Helix Platform SDK and fixes for defects. Additionally, BMC Helix Platform includes the following enhancement: Improved fallback mechanism for displaying localized field values.	Patch 01 for 18.11
November 30, 2018	BMC Helix Platform has been enhanced in the following areas: Foundation library The Foundation data model for Organization and Person data is changed to have more parity with Remedy IT Service Management. Easier conversion between types of Organization and Person. Reduced restrictions on Organization and Person so that customers have more control on Organization and Person data. The Foundation Service REST APIs output structure for Organization data and Person data has changed to match the new data model. The parameters remain unchanged for most parts. Connect to RESTful services in a codeless way from the BMC Helix Innovation Studio UI. Ability to test accuracy, precision, recall, and F-score of BMC Helix Platform Cognitive Service when using for auto-categorization and chatbot. Support for outgoing profiles to enhance the email capabilities. Ability to access attributes such as, complex objects, array of objects, array of strings, and nested complex objects by using a Document definition. Ability to change the layout of view components. Support for customizing user menu to display the user profile. Ability to cancel user-driven approval requests and filter approvers from the foundation data. Ability to edit multiple records in a record grid, define filter presets, and filter rows by cell selection. Responsive web layouts in the browser.	18.11
September 12, 2018	BMC Helix Platform has been enhanced in the following areas: Embed BMC Helix Platform views in external applications. Creation of codeless applications and libraries in a tailoring environment. Using a new PIN field in Foundation data to verify individuals. Configuring approval flows using one single wizard. Introducing Application Business Analyst role in BMC Helix Platform. Enable extension of application definitions. Enhanced load and synchronization of Remedy ITSM Foundation data to BMC Helix Platform. Ability to identify updates to the security label. Enhancements in connectors. Section 508 compliance.	18.08
July 29, 2018	This update includes updated BMC Helix Platform SDK and fixes for defects. Additionally, BMC Helix Platform includes the following enhancements: Zero downtime upgrade of BMC Helix Platform. Audit fields from associated record definitions.	18.05.01
June 6, 2018	BMC Helix Platform has been enhanced in the following areas: Full-text search capabilities in a Digital Service application. Incoming and outgoing email configuration. Deploy code-based application across environments in a dedicated systems. Support for GDPR. Report application errors as issues to customer support.	18.05
March 30, 2018	This update includes updated BMC Helix Platform SDK and fixes for defects. Additionally, BMC Helix Platform includes the following enhancement: Zero downtime upgrade to a new version of an application. BMC applications and partner-developed applications can now be set to have unlimited users in a tenancy.	Update 01 for 18.02
February 28, 2018	BMC Helix Platform includes the following enhancements: Chatbot framework enhancements: Support for multiple chat providers Support for enabling chat conversations through SMS Support for enabling chat conversations through Skype for Business Ability to format chatbot responses Associate and display field values for Approval record definitions Leverage Foundation Data to assign approvers of the approval requests Localize field values of a record definition Localizable Foundation category data Enable row-level security for roles from multiple applications Enable maximum number of training data sets permitted by IBM Watson Assistant for auto-categorization and auto-assignment Support for Remedy Single Sign-On (RSSO) OAuth 2.0 for BMC Helix Platform applications	18.02
January 30, 2018	This update includes updated BMC Helix Platform SDK and fixes for defects. Additionally, BMC Helix Platform includes the following enhancement: Increased limit of training data sets when using BMC Helix Platform Cognitive Service.	Update 01 for 17.11
November 30, 2017	BMC Helix Platform includes the following enhancements: Chatbot framework to provide virtual chat and cognitive search capabilities in your application. Automated assignment using Cognitive Service. Data load and synchronization capability for ITSM Foundation data. Leverage Smart Reporting in BMC Helix Platform application. Remove Mid Tier for tenant configuration: Licensing Management and Assignment. Automatically persist user settings between sessions. Display associations in Approval Console. Hide navigation items in Shell when user does not have permission. Disassociate records to prevent orphaned records. Support RSSO for SAML/IDP based user authentication. Unified logging to improve ability to query across logs. UI improvements for creating and managing Foundation data. Copy fields in a Record. Clear All capability in notification bell. Access error data in caught exceptions.	17.11
October 13, 2017	This update includes updated BMC Helix Platform SDK and fixes for defects.	Update 01 for 17.08
August 25, 2017	BMC Helix Platform includes the following enhancements: Ability to integrate your applications with third-party systems. Support for creating codeless application. Ease of use in deploying applications across environments. Enhancements to improve application development experience.	17.08
July 18, 2017	This update includes updated BMC Helix Platform SDK and fixes for defects. Additionally, following JAR files are no longer bundled with the BMC Helix Platform SDK ( com.bmc.arsys.rx.sdk-17.5.0.zip), as these JAR files are used only for internal framework functionality: com.bmc.arsys.rx.application-test.jar com.bmc.arsys.common.jar com.bmc.arsys.domain.jar To test your application or library, see Testing application logic with the automation framework.	Update 01 for 17.05
May 25, 2017	BMC Helix Platform includes the following enhancements: Ease of application upgrade. Enhancements to address data security and performance. Support for better debugging and troubleshooting your applications. New REST APIs for Foundation library and Approval library. Support for loading Foundation data in bulk. Ease of granting application permissions using Functional Roles. Enhancements to the View Designer interface elements such as Record Grid, Select Group component, and Action button.	17.05
May 09, 2017	This update includes updated BMC Helix Platform SDK and fixes for defects.	Update 02 for 17.02
March 28, 2017	This update includes updated BMC Helix Platform SDK and fixes for defects.	Update 01 for 17.02
February 27, 2017	BMC Helix Platform includes the following enhancements: Lock core platform objects from being customized BMC Remedy Deployment Application now enables you to promote your Digital Service application customization and data across environments	17.02
February 01, 2017	This update includes updated standard library for BMC Helix Platform services and fixes for defects.	IS16.12b
December 22, 2016	This update includes updated standard library and updated Java libraries for BMC Helix Platform services, and fixes for defects.	IS16.12a
December 05, 2016	BMC Helix Platform Developer release.	-

₁ _There_{are no patches with version numbers 20.08.02, 20.08.03, 20.08.06, 20.08.07, 20.08.08, 20.08.10, 20.08.11, and 20.08.14.}

Getting started See more Introduction to BMC Helix Platform The video shows an older version of BMC Helix Platform. The previous product name was BMC Helix Innovation Suite. Although there might be minor changes in the UI, the overall functionality remains the same:		Tailoring applications Customize applications according to your business processes.If you are an Application Business Analyst this is a good place to start. See more Configuring Customize your applications by using Cognitive service, Approval library, and Connectors See more
Onboarding and implementing Set up BMC Helix Platform environment and tailor the environment according to your organizational requirements. See more		Administering Set up users, manage roles, set up Foundation data, assign licenses, submit user reported issues, and create and deploy codeless applications with minimal programming knowledge or dependency on developers.If you are an Administrator this is a good place to start. See more

Developing applications

Develop codeless applications with minimal programming.Develop code-based applications by using the BMC Helix Platform SDK, and Maven archetypes to extend the BMC Helix Platform to create custom components, custom REST APIs, and so on.If you are a Developer, this is a good place to start.

Troubleshooting

Resolve issues with your environment, find solutions to problems while developing or tailoring applications, look up error messages or logs.

Developer Community

BMC Helix Community

Developer Portal

Sample application Product trials

Videos

Podcasts

Marketplace

PDFs, videos, and API documentation

This topic describes and links to PDFs, videos and other documents that support this product release. If the ready-made PDFs of this space do not satisfy your requirements, you can export a custom PDF.

You must log in or register to view this page

Videos

The following list displays the topics that contain videos that supplement or replace the text-based documentation:

20.08 enhancements
- Adding cognitive capabilities to a custom application
  - Adding navigation components to header
    
    BMC Helix Platform 20.08
    
    BMC Helix Platform overview
    
    Configuring actions by using an action button
    
    Configuring approval flows
    
    Configuring self approval flows
    
    Creating a custom service in Java
    
    Creating a Project using Maven and the Archetype
    
    Creating a view for a record instance by using record editor
    
    Creating a view for associating records
    
    Creating an approval process
    
    Creating install packages to deploy entire applications
    
    Creating or modifying regular record definitions
    
    Creating or modifying view definitions
    
    Creating record associations
    
    Creating record instances
    
    Creating update packages to deploy incremental changes of applications
    
    Deploying your Digital Service application for the first time to start working in BMC Helix Innovation Studio
    
    Developing and deploying code-based applications
    
    Developing codeless applications
    
    Facilitating data entry through named lists
    
    Getting your Digital Service application ready for use
    
    Inheriting an existing record definition to a new record definition
    
    Integrating with another application by using a connector
    
    Integrating with REST services in a codeless way
    
    Leveraging Remedy ITSM Foundation data
    
    Localizing a Digital Service application
    
    Navigating BMC Helix Innovation Studio
    
    PDFs, videos, and API documentation
    
    Registering a record
    
    Rule designer elements
    
    Rule designer interface
    
    Setting up your IDE and installing BMC Helix Platform SDK
    
    Toggling between application views and viewing notifications

Frequently asked questions

This topic provides information that supplements the BMC Helix Platform documentation.

Frequently asked questions

This topic provides answers to frequently asked questions (FAQs) about BMC Helix Platform.

What can you do by using Sandbox?

Design and develop your innovative ideas
Build tailorable definitions for your app so that it can be safely customized by your end users
String together the UI of your application
Define your data model and relationships
Configure and tailor existing apps using BMC Helix Platform
Create new workflows, processes or UI using designers
Design and develop new custom components

How do I set account usernames and passwords?

When you first request a Sandbox (on the Developer Portal), you are provisioned two accounts, developer account and administrator account. By default, the developer account is developer and administrator is admin (as shown in the image below). You can specify the account names and passwords.

You can changes the usernames for these accounts and specify the passwords for these accounts. The passwords you specify must meet the following criteria:

Passwords must consist of at least one uppercase character and at least one lower case character.
Passwords must consist of at least one numeric value.
Passwords must consist of at least one special character (any of the following special character ~!@#$%^&*_-).
The length of the passwords must be between 8 to 30 characters.

If I am a BMC customer, do I need to sign-up for the Developer program?

Yes, you still need to sign-up for the program to ensure you benefit from the exclusive Developer content and the Personal Sandbox that will be available only as part of the program.

Do I need to be an existing BMC Customer or Partner to be part of the program?

No, that is not a pre-requisite to sign up for the program.

Can I deploy the application I built in the sandbox into production?

The personal sandbox you get is only a Development Environment. This does not have a Production Environment with a run-time available to deploy applications in the cloud at this time.

How long do I have access to the sandbox?

You have unlimited access to the sandbox as long as you use it. The sandboxes will be reclaimed by BMC if there is a week's worth of inactivity. You will have to request a new sandbox once your sandbox has been reclaimed.

How do I reset developer password?

You can reset the developer password by using Sandbox details page.

On the Sandbox details page, navigate to Manage Your Sandbox > RESET PASSWORD, click RESET PASSWORD.
Select Innovation Suite Developer, enter the new password, and reset the password.

The following image shows the Manage Your Sandbox section:

How do I set the required language for BMC Helix Innovation Studio?

BMC Helix Platform supports the following languages:

German (de)
Japanese (ja)
Russian (ru)
Spanish (es)
French (fr)
Italian (it)
Korean (ko)
Brazilian Portuguese (pt-br)
Chinese (zh-cn)
Swedish (sv)
Dutch (nl)

The following table describes how users can select the required language from various browsers:

Browser	Operating System	Steps to change the language
Google Chrome	Windows, apple MacOS	Open Settings, search for language settings, and add the required language.
Mozilla Firefox	Windows, apple MacOS	Navigate to Open Menu and click Options. Search for language settings and add the required language.
Edge	Windows	In Control Panel, in the Clock, Language, and Region option, add the required languages in the order of preference. You must download the install pack of the added languages and then restart the computer.

BMC Helix Platform also provides localized error messages in the supported locales.

How do I reset Foundation Data user password?

You can reset the Foundation Data user password by using BMC Helix Platform.

Log in to BMC Helix Platform as a developer.
For more information about the roles and their permissions in Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.
org.xwiki.rendering.macro.MacroExecutionException: Failed to get document for reference [confluencePage:page:innovationsuite._inclusionsLibrary]
at com.xwiki.macros.excerptinclude.internal.macro.ExcerptIncludeMacro.internalExecute(ExcerptIncludeMacro.java:130)
at productHelper.macros.BmcExcerptIncludeMacro.internalExecute(BmcExcerptIncludeMacro.java:27)
at productHelper.macros.BmcExcerptIncludeMacro.internalExecute(BmcExcerptIncludeMacro.java:18)
at com.xwiki.macros.AbstractProMacro.execute(AbstractProMacro.java:116)
at org.xwiki.rendering.internal.transformation.macro.MacroTransformation.transform(MacroTransformation.java:311)
at org.xwiki.rendering.internal.transformation.DefaultRenderingContext.transformInContext(DefaultRenderingContext.java:183)
at org.xwiki.rendering.internal.transformation.DefaultTransformationManager.performTransformations(DefaultTransformationManager.java:88)
at org.xwiki.display.internal.DocumentContentAsyncExecutor.executeInCurrentExecutionContext(DocumentContentAsyncExecutor.java:396)
at org.xwiki.display.internal.DocumentContentAsyncExecutor.executeInIsolatedExecutionContext(DocumentContentAsyncExecutor.java:365)
at org.xwiki.display.internal.DocumentContentAsyncExecutor.execute(DocumentContentAsyncExecutor.java:267)
at org.xwiki.display.internal.DocumentContentAsyncRenderer.execute(DocumentContentAsyncRenderer.java:112)
at org.xwiki.rendering.async.internal.block.AbstractBlockAsyncRenderer.render(AbstractBlockAsyncRenderer.java:157)
at org.xwiki.rendering.async.internal.block.AbstractBlockAsyncRenderer.render(AbstractBlockAsyncRenderer.java:54)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.syncRender(DefaultAsyncRendererExecutor.java:290)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.render(DefaultAsyncRendererExecutor.java:267)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRendererExecutor.execute(DefaultBlockAsyncRendererExecutor.java:125)
at org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:67)
at org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:43)
at org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentDisplayer.java:96)
at org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentDisplayer.java:39)
at org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplayer.java:123)
at org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplayer.java:52)
at org.xwiki.display.internal.ConfiguredDocumentDisplayer.display(ConfiguredDocumentDisplayer.java:68)
at org.xwiki.display.internal.ConfiguredDocumentDisplayer.display(ConfiguredDocumentDisplayer.java:42)
at org.xwiki.rendering.internal.macro.display.DisplayMacro.execute(DisplayMacro.java:125)
at productHelper.macros.BmcDisplayMacro.execute(BmcDisplayMacro.java:43)
at productHelper.macros.BmcDisplayMacro.execute(BmcDisplayMacro.java:28)
at org.xwiki.rendering.internal.transformation.macro.MacroTransformation.transform(MacroTransformation.java:311)
at org.xwiki.rendering.internal.transformation.DefaultRenderingContext.transformInContext(DefaultRenderingContext.java:183)
at org.xwiki.rendering.internal.macro.html.HTMLMacro.renderWikiSyntax(HTMLMacro.java:215)
at org.xwiki.rendering.internal.macro.html.HTMLMacro.execute(HTMLMacro.java:150)
at org.xwiki.rendering.internal.macro.html.HTMLMacro.execute(HTMLMacro.java:70)
at org.xwiki.rendering.internal.transformation.macro.MacroTransformation.transform(MacroTransformation.java:311)
at org.xwiki.rendering.internal.transformation.DefaultRenderingContext.transformInContext(DefaultRenderingContext.java:183)
at org.xwiki.rendering.async.internal.block.AbstractBlockAsyncRenderer.transform(AbstractBlockAsyncRenderer.java:76)
at org.xwiki.rendering.wikimacro.internal.DefaultWikiMacroRenderer.transform(DefaultWikiMacroRenderer.java:876)
at org.xwiki.rendering.wikimacro.internal.DefaultWikiMacroRenderer.transform(DefaultWikiMacroRenderer.java:862)
at org.xwiki.rendering.wikimacro.internal.DefaultWikiMacroRenderer.transform(DefaultWikiMacroRenderer.java:595)
at org.xwiki.rendering.wikimacro.internal.DefaultWikiMacroRenderer.execute(DefaultWikiMacroRenderer.java:410)
at org.xwiki.rendering.async.internal.block.AbstractBlockAsyncRenderer.render(AbstractBlockAsyncRenderer.java:157)
at org.xwiki.rendering.async.internal.block.AbstractBlockAsyncRenderer.render(AbstractBlockAsyncRenderer.java:54)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.lambda$syncRender$0(DefaultAsyncRendererExecutor.java:284)
at com.xpn.xwiki.internal.security.authorization.DefaultAuthorExecutor.call(DefaultAuthorExecutor.java:98)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.syncRender(DefaultAsyncRendererExecutor.java:284)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.render(DefaultAsyncRendererExecutor.java:267)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRendererExecutor.execute(DefaultBlockAsyncRendererExecutor.java:125)
at org.xwiki.rendering.wikimacro.internal.DefaultWikiMacro.execute(DefaultWikiMacro.java:109)
at org.xwiki.rendering.wikimacro.internal.DefaultWikiMacro.execute(DefaultWikiMacro.java:53)
at org.xwiki.rendering.internal.transformation.macro.MacroTransformation.transform(MacroTransformation.java:311)
at org.xwiki.rendering.internal.transformation.DefaultRenderingContext.transformInContext(DefaultRenderingContext.java:183)
at org.xwiki.rendering.internal.transformation.DefaultTransformationManager.performTransformations(DefaultTransformationManager.java:88)
at org.xwiki.display.internal.DocumentContentAsyncExecutor.executeInCurrentExecutionContext(DocumentContentAsyncExecutor.java:396)
at org.xwiki.display.internal.DocumentContentAsyncExecutor.execute(DocumentContentAsyncExecutor.java:269)
at org.xwiki.display.internal.DocumentContentAsyncRenderer.execute(DocumentContentAsyncRenderer.java:112)
at org.xwiki.rendering.async.internal.block.AbstractBlockAsyncRenderer.render(AbstractBlockAsyncRenderer.java:157)
at org.xwiki.rendering.async.internal.block.AbstractBlockAsyncRenderer.render(AbstractBlockAsyncRenderer.java:54)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.syncRender(DefaultAsyncRendererExecutor.java:290)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.render(DefaultAsyncRendererExecutor.java:267)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRendererExecutor.execute(DefaultBlockAsyncRendererExecutor.java:125)
at org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:67)
at org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:43)
at org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentDisplayer.java:96)
at org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentDisplayer.java:39)
at org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplayer.java:123)
at org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplayer.java:52)
at org.xwiki.display.internal.ConfiguredDocumentDisplayer.display(ConfiguredDocumentDisplayer.java:68)
at org.xwiki.display.internal.ConfiguredDocumentDisplayer.display(ConfiguredDocumentDisplayer.java:42)
at com.xpn.xwiki.doc.XWikiDocument.display(XWikiDocument.java:1391)
at com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:1527)
at com.xpn.xwiki.doc.XWikiDocument.displayDocument(XWikiDocument.java:1477)
at com.xpn.xwiki.doc.XWikiDocument.displayDocument(XWikiDocument.java:1446)
at com.xpn.xwiki.api.Document.displayDocument(Document.java:788)
at jdk.internal.reflect.GeneratedMethodAccessor547.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:571)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:554)
at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:221)
at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:368)
at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:704)
at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:75)
at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:242)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:439)
at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:190)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.xwiki.velocity.internal.directive.TryCatchDirective.render(TryCatchDirective.java:86)
at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:304)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:439)
at org.apache.velocity.Template.merge(Template.java:358)
at org.apache.velocity.Template.merge(Template.java:262)
at org.xwiki.velocity.internal.InternalVelocityEngine.evaluate(InternalVelocityEngine.java:225)
at com.xpn.xwiki.internal.template.VelocityTemplateEvaluator.evaluateContent(VelocityTemplateEvaluator.java:105)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.evaluateContent(TemplateAsyncRenderer.java:219)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.renderVelocity(TemplateAsyncRenderer.java:174)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.render(TemplateAsyncRenderer.java:135)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.render(TemplateAsyncRenderer.java:54)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.lambda$syncRender$0(DefaultAsyncRendererExecutor.java:284)
at com.xpn.xwiki.internal.security.authorization.DefaultAuthorExecutor.call(DefaultAuthorExecutor.java:98)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.syncRender(DefaultAsyncRendererExecutor.java:284)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.render(DefaultAsyncRendererExecutor.java:267)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRendererExecutor.render(DefaultBlockAsyncRendererExecutor.java:154)
at com.xpn.xwiki.internal.template.InternalTemplateManager.render(InternalTemplateManager.java:904)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderFromSkin(InternalTemplateManager.java:866)
at com.xpn.xwiki.internal.template.InternalTemplateManager.render(InternalTemplateManager.java:853)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderNoException(InternalTemplateManager.java:808)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderNoException(InternalTemplateManager.java:800)
at com.xpn.xwiki.internal.template.DefaultTemplateManager.renderNoException(DefaultTemplateManager.java:79)
at com.xpn.xwiki.internal.template.DefaultTemplateManager.renderNoException(DefaultTemplateManager.java:73)
at org.xwiki.template.script.TemplateScriptService.render(TemplateScriptService.java:54)
at jdk.internal.reflect.GeneratedMethodAccessor8850.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:571)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:554)
at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:221)
at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:368)
at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:492)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:218)
at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:331)
at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:261)
at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:304)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:439)
at org.apache.velocity.Template.merge(Template.java:358)
at org.apache.velocity.Template.merge(Template.java:262)
at org.xwiki.velocity.internal.InternalVelocityEngine.evaluate(InternalVelocityEngine.java:225)
at com.xpn.xwiki.internal.template.VelocityTemplateEvaluator.evaluateContent(VelocityTemplateEvaluator.java:105)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.evaluateContent(TemplateAsyncRenderer.java:219)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.renderVelocity(TemplateAsyncRenderer.java:174)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.render(TemplateAsyncRenderer.java:135)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.render(TemplateAsyncRenderer.java:54)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.lambda$syncRender$0(DefaultAsyncRendererExecutor.java:284)
at com.xpn.xwiki.internal.security.authorization.DefaultAuthorExecutor.call(DefaultAuthorExecutor.java:98)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.syncRender(DefaultAsyncRendererExecutor.java:284)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.render(DefaultAsyncRendererExecutor.java:267)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRendererExecutor.render(DefaultBlockAsyncRendererExecutor.java:154)
at com.xpn.xwiki.internal.template.InternalTemplateManager.render(InternalTemplateManager.java:904)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderFromSkin(InternalTemplateManager.java:866)
at com.xpn.xwiki.internal.template.InternalTemplateManager.render(InternalTemplateManager.java:853)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderNoException(InternalTemplateManager.java:808)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderNoException(InternalTemplateManager.java:800)
at com.xpn.xwiki.internal.template.DefaultTemplateManager.renderNoException(DefaultTemplateManager.java:79)
at com.xpn.xwiki.internal.template.DefaultTemplateManager.renderNoException(DefaultTemplateManager.java:73)
at org.xwiki.template.script.TemplateScriptService.render(TemplateScriptService.java:54)
at jdk.internal.reflect.GeneratedMethodAccessor8850.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:571)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:554)
at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:221)
at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:368)
at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:492)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:218)
at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:331)
at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:261)
at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:304)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:171)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:439)
at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:190)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:439)
at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:190)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:439)
at org.apache.velocity.Template.merge(Template.java:358)
at org.apache.velocity.Template.merge(Template.java:262)
at org.xwiki.velocity.internal.InternalVelocityEngine.evaluate(InternalVelocityEngine.java:225)
at com.xpn.xwiki.internal.template.VelocityTemplateEvaluator.evaluateContent(VelocityTemplateEvaluator.java:105)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.evaluateContent(TemplateAsyncRenderer.java:219)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.renderVelocity(TemplateAsyncRenderer.java:174)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.render(TemplateAsyncRenderer.java:135)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.render(TemplateAsyncRenderer.java:54)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.lambda$syncRender$0(DefaultAsyncRendererExecutor.java:284)
at com.xpn.xwiki.internal.security.authorization.DefaultAuthorExecutor.call(DefaultAuthorExecutor.java:98)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.syncRender(DefaultAsyncRendererExecutor.java:284)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.render(DefaultAsyncRendererExecutor.java:267)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRendererExecutor.render(DefaultBlockAsyncRendererExecutor.java:154)
at com.xpn.xwiki.internal.template.InternalTemplateManager.render(InternalTemplateManager.java:904)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderFromSkin(InternalTemplateManager.java:866)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderFromSkin(InternalTemplateManager.java:846)
at com.xpn.xwiki.internal.template.InternalTemplateManager.render(InternalTemplateManager.java:832)
at com.xpn.xwiki.internal.template.DefaultTemplateManager.render(DefaultTemplateManager.java:91)
at com.xpn.xwiki.internal.template.DefaultTemplateManager.render(DefaultTemplateManager.java:85)
at com.xpn.xwiki.XWiki.evaluateTemplate(XWiki.java:2564)
at com.xpn.xwiki.web.Utils.parseTemplate(Utils.java:180)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:651)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:339)
at com.xpn.xwiki.web.LegacyActionServlet.service(LegacyActionServlet.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:122)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.wysiwyg.filter.ConversionFilter.doFilter(ConversionFilter.java:61)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.container.servlet.filters.internal.SetHTTPHeaderFilter.doFilter(SetHTTPHeaderFilter.java:63)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.resource.servlet.RoutingFilter.doFilter(RoutingFilter.java:132)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:208)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:542)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:687)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:764)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:354)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:382)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:888)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1684)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: com.xpn.xwiki.XWikiException: Error number 3202 in 3: Exception while reading document [confluencePage:page:innovationsuite._inclusionsLibrary()]
at com.xpn.xwiki.store.XWikiHibernateStore.loadXWikiDoc(XWikiHibernateStore.java:1233)
at com.xpn.xwiki.store.XWikiCacheStore.loadXWikiDoc(XWikiCacheStore.java:399)
at com.xpn.xwiki.XWiki.getDocument(XWiki.java:2195)
at com.xpn.xwiki.XWiki.getDocument(XWiki.java:2257)
at com.xwiki.macros.excerptinclude.internal.macro.ExcerptIncludeMacro.internalExecute(ExcerptIncludeMacro.java:128)
... 232 more
Caused by: com.xpn.xwiki.XWikiException: Error number 2 in 0: No wiki with id [confluencePage:page] could be found
at com.xpn.xwiki.internal.store.hibernate.HibernateStore.beginTransaction(HibernateStore.java:854)
at com.xpn.xwiki.store.XWikiHibernateBaseStore.beginTransaction(XWikiHibernateBaseStore.java:576)
at com.xpn.xwiki.store.XWikiHibernateStore.loadXWikiDoc(XWikiHibernateStore.java:1082)
... 236 more, see Roles-and-permissions.
On the Administration tab, click Administration > Foundation Data > Manage People > All People.
Select the user for whom you want to change the password, click Edit, and navigate to the Basic tab.
On the Basic tab, click Access Details.
In Password, enter the new password, and click Save.

How do I unlock an account?

If you encounter the error ERROR 624 User account locked, when you login to BMC Helix Innovation Studio, navigate to the Sandbox details page, and click Unlock Account.

How are test metrics calculated for BMC Helix Platform Cognitive Service?

Example of how cognitive test metrics are calculated

You have created a data set to test whether BMC Helix Platform Cognitive Service can categorize appropriate service requests in Category A and Category B. The following table indicates the number of expected and predicted categories:

	Expected Category A	Expected Category B	Total Predictions of expected categories
Predicted Category A	8	4	12
Predicted Category B	2	6	8
Total predictions for A and B	10	10	20

Based on the above results, the accuracy, precision, recall, and F-score for Category A and Category B are calculated as shown in the following table:

Test metrics	Category A	Category B
Accuracy	8/10 = 0.8	6/10 = 0.6
Recall	8/10 = 0.8	6/10 = 0.6
Precision	8/12 = 0.67	6/8 = 0.75
F-score	2* (0.80*0.67)/ (0.80 + 0.67)	2* (0.60*0.75) / (0.60 + 0.75) = 0.66

The consolidated results for BMC Helix Platform Cognitive Service for Category A and Category B are calculated by using the weighted macro average as shown in the following table:

Test metrics	Formula	Result
Accuracy	10/200.80 + 10/200.60	0.70
Recall	10/200.80 + 10/200.60	0.70
Precision	10/200.67 + 10.200.75	0.71
F-score	2(0.700.71) / (0.70+0.71)	0.70

Note

For multi-class categories, Accuracy and Recall that is computed for each category and the consolidated calculation for BMC Helix Platform Cognitive Service are the same.

What do I do when I get the error 'You are not authorized to access BMC Helix Innovation Studio?'

If you encounter the error You are not authorized to access BMC Helix Innovation Studio when you log in to BMC Helix Innovation Studio, use your developer account to log in. This error occurs when you try to log in to BMC Helix Innovation Studio by using an administrator account.

What do I do when BMC Helix Innovation Studio locks constantly?

If you encounter the following error even if you do not have any failed login attempts:

ERROR (624): User account locked out due to too many failed login attempts. Please contact your Administrator.; developer

In this case, you should create a new account in BMC Helix Innovation Studio and use the account for development. To create a new account, perform the following steps:

Log in to BMC Helix Innovation Studio.
Navigate to Administration > Configure My Server > People > Manage User Accounts.
Create a user with Administrator permissions and a fixed license.

How do I access database record and transaction record in a process?

To access the transaction record of a rule, you can use record as the process input, and have rule call process and pass the transaction record. See Working with rules.
To get the database value of a record, you can use Get Record action, and access the database value using the activity results of the Get Record action. See Get Record action.

How to use transaction (TR) field or DB field in rule qualification?

In rule qualification, you can use the function NEWVALUE() for TR field and the function OLDVALUE() for DB field. See Working with rules.

How do I create display only field to store action results?

You do not need the display only field to store the activity results. In a process, you can get the activity results in the following ways:

You can use the expression ${activityResults.<activityGUID>.xxx> to access an activity output.
All activity results are stored in the process context and can be accessed anywhere.
If an activity is not executed, you get an empty value.
If an activity returns a record (that is Get Record Service Task), only the record identity (record ID and record definition name) is persisted to the process context. Record field values are not persisted to the process context.
If you access field values of Get Record Service Task, you get the latest database value of the record. See Get Record.
You can use the activity Output Map to store activity result in a process variable.

How does a process transaction works in process runtime?

When a process is started through an API (Record API triggers rule, which starts the process or Start Process API), process transaction starts at the REST APIs.

The process transaction joins the API transaction and the process runs till its completion or it is goes to a wait step. Wait steps are User Tasks or Receive tasks. When the process reaches a wait step, it persists all the transaction values and returns from the wait state. When the process resumes the execution from a wait step, the process transaction continues till it completes or reaches the next wait step. The records, signal inputs, process operations, process context, and the wait state information are all persisted in one transaction.

For more information on APIs, see PDFs-videos-and-API-documentation.

For more information on User Tasks and Receive tasks, see Activities.

How are process instances managed?

Process instances are managed by the platform and third party process engine Activiti. The platform manages process context and Activiti engine manages process instance state information.

Process context consists of process variables and process activity results.
Process instance state information consists of process current activity, start time of a process, and end time of completed process activities.

For process context, there is a form to store active process instances, and a form to store completed process instances. The archive policy of completed process instances is that all completed process process instances are moved to an archive form after three months. Process instance state information follows the similar pattern.

How does a process instance resumes from User Task?

The condition to resume a process instance from User Task is specified in the Completion Criteria property of User Task (process designer element). Completion Criteria specifies the condition when the user task is considered as complete. The condition is an expression that evaluates fields of a task record.

The platform service EntryEventNotificationService is used to monitor registered record events. User Task uses EntryEventNotificationService to monitor the task completion. Records that need to be monitored are registered in the Entry Event Registration system form and the Notifier Listening field is set to true.

When a record event occurs, the EntryEventNotificationService evaluates the record instance condition and if the condition is true, the Pending Notification flag is set.
A background thread notifies event listeners of all pending notification records with the Notification Information provided by the record event register. When the listener is notified, the record event is cleaned up from the registration form and the Notifier Listening flag is reset. Event listeners are notified by a separate pool of threads where the pool size can be configured.

Where are my overlay objects?

To make the platform operational in varied customer environments, the way you customize objects in core BMC applications has changed from 17-02 onwards. You can customize the objects developed in your own applications, but you cannot customize the objects developed in com.bmc.arsys. For example, objects in core BMC applications like Foundation, Approval, and Assignment cannot be customized. You cannot customize the record definitions by updating the permissions or adding security labels, adding or updating record fields, and so on. Therefore, you must delete the customizations and then perform the upgrade the BMC Helix Platform. If you attempt to customize any objects developed in core BMC applications, you encounter the following error message:

If you attempt to customize any objects developed in core BMC applications, you encounter the following error message:

Why are the required Default Tenant field values displayed empty?

In BMC Helix Platform, you may find the required fields of the Default Tenant (Administrator > Configure My Server > Manage Tenants) such as Domain Identifier and Virtual Host Name are empty. This is because the default tenant fields are imported during the platform creation and when you use tools such as data import there is an option to not trigger the required field check.

I am unable to export a licensed application that includes definitions and data? What do I do?

If you are working on a dedicated system, ensure that you have assigned the application license to yourself using the Foundation Person UI. For more information, see Creating-or-modifying-Person-data.

I am unable to see my licensed application. What do I do?

To see a licensed application, you must have that application license assigned to you using the Foundation Person UI. For more information, see Creating-or-modifying-Person-data.

Application upgrade FAQs

How do I enable logging for applications that are created by using BMC Helix Platform 17.02 or earlier?

The logs for applications created using the BMC Helix Platform SDK 17.02 or earlier are stored in the arextension.log file located at the following location:

Windows: <ARSystemInstallDir>\Arserver\Db
UNIX: <ARSystemInstallDir>/Arserver/Db

By default, only error messages are logged. If you want to log all messages (debug, info, warning, and error), you must change the log level to debug in the logback_server.xml file. The following configuration enables debug log level:

Note

When you make changes to the logback-server.xml file, you do not need to restart the Remedy AR System server. After making the changes to the logback_server.xml file, you must reload the file by using the Reload Log Conf File option in the Server Information form on the Log Files tab.

The logback logging framework provides this logging functionality.

Related spaces

BMC Helix

Helix Chatbot

Helix Business Workflows

Digital Workplace Advanced

Remedy Single Sign-On

18.08 18.11 19.02 19.05 19.08 19.11 20.02 20.08

Remedy IT Service Management Suite

20.02

BMC Helix Platform 20.08