Where to edit Process Designer artifacts
| Artifacts | Editable in the desktop Process Designer | Editable in the Process Designer |
|---|---|---|
| Traditional: Advanced Integration Service (AIS) |
Yes | Yes |
|
Traditional: Ajax Service (deprecated) |
Yes | In Process Designer, you use a service flow with the appropriate Ajax access defined. To convert an Ajax service to a service flow, see Mapping Ajax service artifacts. |
| Blueworks Live Subscription | Yes | Yes |
| Business Object | Yes | Yes |
|
Traditional: Business Process Definition (BPD) (deprecated) |
Yes | In Process Designer, you can launch a BPD as a linked process from a process. To convert BPDs to processes, see Converting BPDs to processes. |
| Chart Type | Yes | No |
| Client-Side Human Service | No | Yes |
| Content Management toolkit | Yes | Yes |
| Content Objects | Yes | Yes |
|
Traditional: Decision Service (deprecated) |
Yes | In Process Designer, use a service flow. To convert a Decision service to a service flow, see Mapping Decision service artifacts |
| Decision support in Service Flows | Yes | Yes |
|
Traditional: Design File |
Yes | Yes |
|
Traditional: Document Type |
No | Yes To use document types, you must have installed the Basic Case Management feature from a previous release |
| Event Subscription | Yes | Yes |
| Exposed Process Value | Yes | Yes |
|
Traditional: External Implementation |
Yes | Yes In Process Designer, you create an External Service with an External Implementation binding. |
| External Service: REST service | No | Yes |
| External Service: Java™ service | No | Yes |
| External Service: Web service | No | Yes |
|
Traditional: General System Service (deprecated) |
Yes | In Process Designer, use a service flow instead of a general system service. To convert a General System service to a service flow, see Mapping General System service artifacts. |
| Traditional: Heritage Coach (deprecated) |
Yes | Yes Heritage coaches are not
supported in a Container runtime environment. |
| Heritage Human Service (deprecated) | Yes | Yes Note that heritage coaches included in heritage human services are not
supported in a Container runtime environment. |
|
Traditional: Historical Analysis Scenario (deprecated) |
Yes | No |
|
Traditional: IBM® Case Manager Integration Service (deprecated) |
Yes | In the Process Designer, use a process with ad-hoc activities instead of the IBM Case Manager Integration Service. |
|
Traditional: Integration Service (deprecated) |
Yes | In Process Designer, use a service flow instead of an integration service. To convert an Integration service to a service flow, see Mapping Integration service artifacts. |
|
Traditional: Key Performance Indicator (KPI) |
Yes | No |
| Layouts (Chart Type, Report Filter, etc.) | Yes | No |
|
Traditional: Localization Resource |
Yes | Yes |
| Process | No | Yes |
| Process Application Setting All settings are not available in both Process Designer editors. To see the difference, open the process app editor in the desktop and Process Designer and compare the two. |
Yes | Yes |
| Report | Yes | No |
| REST service (inbound) | No | Yes |
| ScoreBoard | Yes | No |
| Server File | Yes | Yes |
| Service Flow | Yes | |
|
Traditional: Service-Level Agreement (SLA) |
Yes | No |
|
Traditional: Simulation Analysis Scenario (deprecated) |
Yes | No |
| System Data toolkit | Yes | Yes |
| Team | Yes | Yes |
| Theme | No | Yes |
|
Traditional: Timing Interval |
Yes | No |
| Tracking Group | Yes | Yes |
| Undercover Agent | Yes | Yes |
| User Attribute Definition | Yes | Yes |
| View | Yes | Yes To use responsive features in views, for example, to have the runtime behavior respond to different screen size environments, you must edit views in the Process Designer. Positioning and grid are also available only in the Process Designer. To convert deprecated coach views into UI views, see Mapping deprecated functions to UI functions. |
| Web File | Yes | Yes |
| Traditional: Web Service (inbound) |
Yes | Yes |