Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Established Member.. Ben.Shirley
Established Member..
1264 views

Questions around Process Designer.

Jump to solution

Hi Experts,

 

RTE: 9.34

App: 9.31.0022

 

We have a few questions around the implementation of the process designer.

 

  1. If we duplicate our heavily customised current production environment, are we able to apply process designer content pack v9.30.3 to our version?

 

  1. Once we apply the content pack, are we able to turn it on but only for one of our least custom modules say the problem module only?

 

  1. If we turn it on for a module, what tailoring gets turned off, and if it is turned off is it kept in the system, with suggestions given on how to migrate it etc?

 

Any help and general direction appreciate,

 

Thanks!

0 Likes
1 Solution

Accepted Solutions
Highlighted
Absent Member.. John Stagaman Absent Member..
Absent Member..

Re: Questions around Process Designer.

Jump to solution

1. If we duplicate our heavily customised current production environment, are we able to apply process designer content pack v9.30.3 to our version?

--Yes, but you'll need to decide how to best approach the migration of current records to new PD workflows.

A. You could start with the new OOB workflows and forms, migrating selected elelments of your customized system to the new workflows, but leveraging out of box. 

B. You could start with you existing structures, and a very simple workflow (basically: open, update, resolve, close) using your current forms while adding only the PD elements needed. Your current format control could still be called.

C. Anything in the middle, where you either modify the new stuff a lot, or you layer more new functionality into build starting from your current build, such as:

  --now might be a good time to do HTML notification.

  --Hey, suspend works really well in the new PD flows. Maybe add that. 

  --Maybe move to the OOB flow for Interactions and decide to manage non-incident category issues as interactions, without escalating them to incident? 

  --You get IM Tasks for free!

 

2. Once we apply the content pack, are we able to turn it on but only for one of our least custom modules say the problem module only?  

--If you apply the any PD content pack, change management is automatically migrated to PD.

--If you enable PD for Help Desk, Interaction, Incident & Problem all convert to PD. They cannot be enabled separately.

 

3. If we turn it on for a module, what tailoring gets turned off, and if it is turned off is it kept in the system, with suggestions given on how to migrate it etc?

--PD replaces the old display screens and docengine components with new ones, so any tailoring at that level would need to be migrated or implemented using PD tools. 

--PD workflows still call almost all legacy tailoring elements. Form-level format control, for example. Master FC is not called oob, but can be if you update the object record (the master format control field is blank oob>

--PD moves to new source tables for category/subcategory/area, but it is possbile to tailor to still use the old tables if you need to. 

--PD Help Desk worlkflows don't call the notification engine--they call HTML Email RuleSets out of box. PD Change calls the legacy notificaiton records, but from rulesets (at the time Change PD was developed HTML Email was not yet part of the base build.

----------------------------------------------------
Kudos - what, where, how, and why
Want Good Answers? Ask Good Questions...
3 Replies
Acclaimed Contributor.. Vadim Gorda Acclaimed Contributor..
Acclaimed Contributor..

Re: Questions around Process Designer.

Jump to solution

Hello,

You will still need clarifications on my replys as I have not done it personal, but what I heard:

 

 

  1. If we duplicate our heavily customised current production environment, are we able to apply process designer content pack v9.30.3 to our version? - 9.34 did not had PD pack in it so ost obvious that you can use the previous content pack (we installed 9,34 pack and it lives with PD)

 

  1. Once we apply the content pack, are we able to turn it on but only for one of our least custom modules say the problem module only? - As I remember that way seeparated was only change. Rest modules were hit by PD at a time.

 

  1. If we turn it on for a module, what tailoring gets turned off, and if it is turned off is it kept in the system, with suggestions given on how to migrate it etc? - fc and related as I know. It is not removed from the system so you can modify and try to tailor it as well.
Highlighted
Absent Member.. John Stagaman Absent Member..
Absent Member..

Re: Questions around Process Designer.

Jump to solution

1. If we duplicate our heavily customised current production environment, are we able to apply process designer content pack v9.30.3 to our version?

--Yes, but you'll need to decide how to best approach the migration of current records to new PD workflows.

A. You could start with the new OOB workflows and forms, migrating selected elelments of your customized system to the new workflows, but leveraging out of box. 

B. You could start with you existing structures, and a very simple workflow (basically: open, update, resolve, close) using your current forms while adding only the PD elements needed. Your current format control could still be called.

C. Anything in the middle, where you either modify the new stuff a lot, or you layer more new functionality into build starting from your current build, such as:

  --now might be a good time to do HTML notification.

  --Hey, suspend works really well in the new PD flows. Maybe add that. 

  --Maybe move to the OOB flow for Interactions and decide to manage non-incident category issues as interactions, without escalating them to incident? 

  --You get IM Tasks for free!

 

2. Once we apply the content pack, are we able to turn it on but only for one of our least custom modules say the problem module only?  

--If you apply the any PD content pack, change management is automatically migrated to PD.

--If you enable PD for Help Desk, Interaction, Incident & Problem all convert to PD. They cannot be enabled separately.

 

3. If we turn it on for a module, what tailoring gets turned off, and if it is turned off is it kept in the system, with suggestions given on how to migrate it etc?

--PD replaces the old display screens and docengine components with new ones, so any tailoring at that level would need to be migrated or implemented using PD tools. 

--PD workflows still call almost all legacy tailoring elements. Form-level format control, for example. Master FC is not called oob, but can be if you update the object record (the master format control field is blank oob>

--PD moves to new source tables for category/subcategory/area, but it is possbile to tailor to still use the old tables if you need to. 

--PD Help Desk worlkflows don't call the notification engine--they call HTML Email RuleSets out of box. PD Change calls the legacy notificaiton records, but from rulesets (at the time Change PD was developed HTML Email was not yet part of the base build.

----------------------------------------------------
Kudos - what, where, how, and why
Want Good Answers? Ask Good Questions...
Established Member.. Ben.Shirley
Established Member..

Re: Questions around Process Designer.

Jump to solution

Thanks, some good information there.

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.