APIs, SDKs, and Services > Screenflow Programming and SDK > About ActiveVOS Platform SDK

About ActiveVOS Platform SDK

The Platform SDK contains a business user tool for workflow development called the Guide Designer. The guide designer has a simple interface for creating steps such as screens and automated actions and they can use and modify data in a host system. The guides that you create are applications that run from within a web browser connecting to either an internal or external server. The browser can be within a PC or a computer created by Apple.
The Host Provider SDK and associated Service Programming Interface (SPI) allow developers to expose data and operations in their host system to the Designer. At the heart of the system are reusable services that are defined using the powerful Process Developer environment and deployed to the Process Server environment. These services implement the SPI necessary for providing a hosting environment (Host Provider) and are described to the Process Servr using a simple descriptor mechanism

Sample Guide Designer Orchestration Project Templates

Project Developer has three sample Guide Designer orchestration project templates:
Each of these projects has its own cheat sheet that will guide you through using them.
Note: Do not deploy more than one of these projects at the same time. If you do, you will see an error dialog with the following message 'Application is not correctly configured' when you are using Process Central'. This occurs because each sample project has its own configuration file and only one can exist. Correct this problem by going to the Process Console, selecting Catalog | Contribution, clicking on a contribution's link, then deleting one of the projects.

Guide Designer Host Provider Template

The easiest way to get started is by installing the Guide Designer Host Provider sample project provided with the Process Developer and which runs sin the Process Designer environment. The Process Developer has an orchestration project template sample for creating a Host Provider. Simply select File > New Project > Orchestration Project, enter a project name, and then select Guide Designer Host Provider Template to set up the project in your workspace.
Sample Project Contents
The sample project contains resources that illustrate how to use an SQL database as the host application on which Process Designer will operate. All screens operate on one or more entities that are contained within a database table. Internally, this sample uses the Data Access system service provided by Process Server to connect to the database with a JDBC connection configured in JNDI.
BPEL Folder
The bpel folder contains the following resources:
The deployment artifacts for each of these BPEL process are in the deploy directory.
Config Folder
The config folder contains resources typically found in many projects:
db_schema Database Artifacts Folder
The db_schema folder in the sample project provides the DDL for some common databases that creates the tables required by the guides packaged with the sample. The included Derby database is prepopulated with a schema and sample data.
This sample has two folders:
Sample guides are in the guides folder. These are imported and published during when the sample is deployed.
host_env Environment Definition Folder
The host_env folder contains the definitions of all entities used by the host application. In this sample, each table in the database schema is mapped to a single entity in this folder. For example, the contacts table is represented by the contacts_detail.xml file. In addition, the entityList.xml file is a master index of all entities that will be deployed.
Other Resources
The icons folder has images that guide designers can use and which are used by published guides. Other folders containing data are deploy, sample-data, and xquery.

Sample Customization Starter Template

The Sample Customization Starter template can be used as a starting point for creating service call steps and custom themes for use in Guide Designer  Simply select File > New Project > Orchestration Project, enter a project name, and then select Guide Designer Customization Starter to set up the project in your workspace. The following sections describe the contents of this project.
BPEL Processes
The bpel folder contains the HelloWorld.bpel file that is based on the HelloWorldAutomatedStep system service. The service receives a name and returns a Hello World-type of greeting based on the time of day. The process demonstrates the use of a complex-type response and shows a complex type being rendered for display in HTML and uses JavaScript and related technologies for this purpose. You must always create a custom renderer for your custom types.
Deployment artifacts for these BPEL process are in the deploy directory.
This folder contains the definition for the "Hello World" guide. It also contains the system-generated guide-catalog.xml file.
A guide is the application that users build in Guide Designer. (Application developers can also create them within Process Developer and Process Designer.) The guide within this folder has a few step types, including a service call step. This step is essentially the HelloWorld.bpel process. All of your application's guides will reside in the guides folder.
The folders in the forms folder define two of the components that Process Central displays as part of its user interface: the guide explorer and the guide viewer. Use the code in the following folders to see how each was created. You can also use this code if you wish either to create your own explorer or viewer or modify the ones that exist..
The samples-starter.avcconfig.xml contains information used when configuring form filters.
avcconfig files here and in other folders control how Process Designer resources are used in a project.
Note: The Process Server executes your avcconfig files in alphabetical order. You can see this order by selecting Catalog | Resources | Central Configs from within the Process Console. If one of your files is inadvertently overriding another, you will need to change the file's name to change the execution order.
The reports folder contains the files needed to construct the guides report that displays within Process Central. Use the information in this folder as the basis for creating your own reports. (This report, like other reports used in Process Central, was created using BIRT--Business Intelligence and Reporting Tools.) The avcconfig file contains sections that are commented out, and you should uncomment them if you are creating your own versions.
Guide Designer
The guides folder contains the resources that the project requires, some of which are deployed in the project deployment contribution and others that you must import directly into Guide Designer. Open the .xml files within each of the subfolders to see what was done for this project.
This folder contains four additional folders as well as the app-config.xml file.
The folder also has the app-config.xml configuration file. This file has design-time and run-time properties for Guide Designer that declared to be used by the host provider This configuration defines features supported by the host platform as well as possible overrides to Guide Designer.
Note: There can be no more than one app-config.xml file on a server.

avcconfig Files Used in the Sample Orchestration Templates

ActiveVOS applications contain forms, tasks, and reports, as well as other resources. A basic configuration file resides in Process Server to provide the initial configuration for navigation filters. ( You can view the file from the Catalog Resources page of the Administration Console) You can create additional configuration files that customize the navigation filters on a user-by-user or group-by-group basis, and also describe the forms and reports to be deployed.  Your modifications override the basic settings.
Here is a description of the avcconfig files used in the sample orchestration templates.
Screenflow Demo
Screenflow Customization Starter
Screenflow Host Provider Template

Deploying the project

This topic describes how you deploy the sample application.
Setting Up the Database (Guide Designer Host Provider Only)
The sample application uses the embedded Process Server database that ships with Process Developer. If you are using this database, it is set up for you. If you wish to use an external database, you will need to do the following to use the new JNDI data source:
  1. 1. Configure your Process Server with an additional JNDI data source.
  2. 2. Deploy the DDL provided with the sample.
  3. 3. Update the PDD for the dbHostEnvironmentRuntime.
Setting Up the Server
The steps for setting up the server are as follows:
  1. 1. Start the embedded Process Server. This is described in the Process Developer help.
  2. 2. Right click on the .bprd file (for example, ae-db-cloudprovider.bprd) and choose Execute from the context menu.
  3. 3. Update the URN mapping. Set aeHostEnvironmentRuntime to dbHostEnvironmentRuntimeService.

Using the Sample Host Provider

This topic describes running the guides within the sample projects.

Running the Sample Guides

Run the sample guides as follows:
  1. 1. Navigate to http://localhost:8080/activevos-central in your browser.
  2. 2. Log in as loanrep1/loanrep1.
  3. 3. Choose Forms from the left navigation pane.
  4. 4. Click on the Published Guide Designers folder.
  5. 5. Choose one of the sample guides.
  6. 6. After the guide loads, follow its prompts.

Mobile Guide Usage

To convert any guide to a mobile guide, begin by changing the theme to "Smartphone" in the Guide Properties dialog. The size difference between the screen and a phone could mean that you may have to rearrange and perhaps simplify steps.

Customizing the Sample Host Provider

This section discusses customizations that you can make to the sample project. They demonstrate how you define a new type that provides links to a mapping service such as Google Maps. The first step is defining a JavaScript renderer and defining a custom data type. (Rendering is the application of a friendly user interface for the task's interface input and output messages.) Next, modify the project's metadata files that allow these additions to be discovered.
Note: The Process Server executes your project's .avcconfig files in alphabetical order. You can see this order by selecting Catalog | Resources | Central Configs from within Process Console. If one of your files is inadvertently overriding another, you will need to change the file's name to change the execution order.
Note: When implementing a custom renderer, you must add the ae-sf-renderer-container class to the root element (that is, to the <div>) of your renderer. If you do not, your interface will open in a new window.
Custom Type Example
Creating a custom data type requires that the new type be defined in a metadata file and a renderer be defined to display it at both design- and runtime.
In the example, {$sample.project}/config/MapItRenderer.js renders an HTML anchor with the text "Map It" and the href of the anchor is a URL to a mapping service configured in the datatype options.
Code Example: Renderer JavaScript
(function($) {
function MyCustomRenderer(aDataValueCollection) {
this.renderField = function(aContainerElement,
ajQueryContext, aFieldName, aFieldDataValue)
// do something
my.custom.namespace.MyCustomRenderer = MyCustomRenderer;
This example is a skeleton for a custom renderer and it only requires that the renderField function be implemented. The second line defines a unique package name or namespace for the renderer; this is similar to a package name in Java.
The lines shown in bold begin the definition of the custom renderer function. It accepts an argument (shown in the next example) that contains all of the data for the screen. It also defines the renderField property, which is also a function and which renders the data. The renderField arguments are the HTML elements that contain your custom rendered field, the jQuery context, the field name being rendered, and the field value (see the AeScreenFlowDataValue example later in this topic).
Code Example: AeScreenFlowDataValuesCollection Function
function AeScreenFlowDataValuesCollection(){
* @returns {Array} list of AeScreenFlowDataValue objects.
this.getDataValues = function() {};
* @returns {boolean} true if named data value holder
* exists.
this.hasDataValue = function(aName) {};

* Returns a type by name or null if not found.
* @param {String}: aName name of data value
* @returns {AeScreenFlowDataValue}; the data value or null
* if not found.
this.getDataValue = function(aName) {};
Code Example: AeScreenFlowDataValue Function
function AeScreenFlowDataValue(aType, aName, aValue, aRenderingTypeName) {
* Gets the rendering type name. If the rendering type is not
* set, it returns the type.
this.getRenderingTypeName = function() {};
* Gets the name of the field.
this.getName = function() {};

* Gets the value of the field.
this.getValue = function() {};

* @returns {AeDataOptions} Collection of AeOption objects.
this.getOptions = function() {};

* Returns option value.
* /
this.getOptionValue = function(aName) {};

* @returns {boolean} true if field is readonly.
this.isReadOnly = function() {};
After you define the renderer, you can define the custom type. The {$sample.project}/config/custom-types.xml sample project defines a new type named mapit. It is bound to the MapitRenderer.js custom renderer. To enable this type for the sample application, uncomment the type element.
Using JavaScript Libraries
When a custom renderer uses a JavaScript library, it can import it dynamically instead of including it within an avcconfig file. For example, you could load a library named dataTable as follows:
var loadDataTablePlugin = $.dataTable ? null :
myProject.loadScript(/path/to/datatable/js/file, $);
$.when(loadDataTablePlugin).done( function() {
// Use dataTable here}
Customizing an Entity
After creating the custom types and renderers, you need to make them available for your host application. The project does this by using the mapit type in the custom contacts entity to provide a Google Map for the contact. In the {$sample.project}/host_env/contacts_detail.xml file, uncomment the field definition for Full Address.
Code Example: Full Address Field Definition
<host:field label="Full Address" name="FullAddress"
readonly="true" required="false" type="mapit">
<host:option name="mapping-provider"
The mapping-provider attribute's value was changed to use Microsoft Bing as the mapping provider instead of Google Maps. The mapping-provider option is hidden so that guide developers cannot edit it. If the hide attribute was set to false or removed, guide developers could change the mapping-provider in the guide designer.
After altering the entity definition, redeploy the sample project using the packaged BPRD file, as follows:
After you launch the updated guide, a new Map It link appears that opens a new browser tab when clicked.
Validating Fields
A render class can implement the validateField JavaScript function to validate data. This function is called when the user presses an action button.
This function's definition is:
validateField(aFieldDataValue, aJQueryContext)
Here's an example:

this.validateField = function(aFieldDataValue, aJQueryContext) {
var $ = aJQueryContext;
var salutation = aFieldDataValue.getValue().salutation;
if ( salutation.name.$t === 'chester'){
var errorMsg = "Cant equal chester";
return { result: false, message: errorMsg};
return { result: true };