[ https://issues.jboss.org/browse/JBDS-1801?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick reassigned JBDS-1801: --------------------------------------- Assignee: Kris Verlaenen Kris, can you work with Isaac to make sure the language matches the tooling? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1801?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-1801: ------------------------------- Fix Version/s: 4.1.1 Affects Version/s: 4.1.0.GA -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1801?page=com.atlassian.jira.plugin.... ] Kris Verlaenen commented on JBDS-1801: -------------------------------------- RuleFlow is a specific type of Process, for rule orchestration. We migrated from "RuleFlow" to the more generic "Process" on purpose. I would suggest simply updating the documentation with an up-to-date screenshot? Or is there any reason why this really needs to be RuleFlow? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1801?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-1801: ------------------------------- Priority: Minor (was: Critical) Note from Kris - we can close this and just put a short note in the docs ======================= The wizard allows you to create a "Process". Should it be the case that this process is about rule orchestration, we would indeed call it a "RuleFlow" (with or without space . In BRMS 5.2, only "RuleFlow" is _supported_, so it is more likely that people that use this wizard in this context are creating a "RuleFlow". But the same tooling is not only used in that context, but also in a much broader context (using unsupported features, or simply in the community), where "Process" is a name that in general covers all use cases. So the BRMS 5.2 docs are correct to talk about "RuleFlow" as that is what they should be using the process for (if they stick to supported features). But changing the name to "RuleFlow" would be confusing for all users that are using it to create something that isn't a RuleFlow, but a more generic Process. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1801?page=com.atlassian.jira.plugin.... ] Isaac Rooskov commented on JBDS-1801: ------------------------------------- Len, thanks for that. I feel that any BRMS documentation referring to this should be updated in order to talk about using the 'Process' wizard to create a 'Rule Flow'. I will pass this on to the BRMS docs lead ;) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira