Question
Accenture
SG
Last activity: 24 Jul 2019 10:10 EDT
Node classification in Pega 7.3
I've got a few queries regarding node classification in Pega 7.3. We're running Pega Marketing 7.22 on this.
I've got a few queries regarding node classification in Pega 7.3. We're running Pega Marketing 7.22 on this.
- Can we use more than 5 Custom node types in Pega 7.3? The documentation here only mentions that we have 5 custom node types.
- Can the custom node types be renamed? In a forum post I found here, someone from Pega has said that it cannot be done. However I also saw in documentation here that "You can create custom node types by specifying them in the
applicableNodeTypesJVM argument. " This seems to imply that we can have as many custom node types as needed and that we can name them as we please. - We've been advised to have nodes for the purposes listed below. For each node type below, which OOTB listeners and agents must be associated? Where should the custom agents and listeners fall under? Is there any documentation available that gives guidance on this?
|
Data Flow |
|
Decision Data Service |
|
ADM |
|
VBD |
|
Database |
|
Decision Hub |
|
Util/App. Tier |
Thanks!
***Moderator Edit-Vidyaranjan: Updated Platform Capability***
Pegasystems Inc.
US
See the replies:
1. No, only possible after 8.x.
2. No, only possible after 8.x. So the doc is only applicable for the recent 8.x release.
3. Not aware of any public docs, but the latest releases from Platform already associate agents to the right node types, mostly ‘BackgroundProcessing’
Accenture
SG
Hi Kevin,
Thanks for responding.
We want to have 7 custom node types, and don't need the other default node types like "BIX" or "Search". As such can we just make use of Custom1 to Custom5 and use BIX and Search for the remaining two? They are just names after all, correct? The only downside is that it may cause confusion, but technically it would be consequential. Please confirm or correct my understanding.