Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BXMSDOC-4014 7.4 Release Notes #175

Merged
merged 18 commits into from Jul 10, 2019

Conversation

emmurphy1
Copy link
Owner

See jira for details:
BXMSDOC-4014

ifdef::PAM[]
[NOTE]
====
{PRODUCT_DM} fixed issues apply to {PRODUCT_PAM} as well. See the https://access.redhat.com/documentation/en-us/red_hat_decision_manager/7.3/html-single/release_notes_for_red_hat_decision_manager_7.3/index[_Release Notes for Red Hat Decision Manager 7.3_] for a list of {PRODUCT_DM} 7.3.0 fixed issues.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change {PRODUCT_DM} versions to 7.4 and 7.4.0.

Should the phrasing be changed to the IBM SG style. For example:
"For a list of {PRODUCT_DM} 7.4.0 fixed issues, see the https://access.redhat.com/documentation/en-us/red_hat_decision_manager/7.3/html-single/release_notes_for_red_hat_decision_manager_7.4/index[_Release Notes for Red Hat Decision Manager 7.4_]"

For future RNs, is it possible to use constraints to avoid linking to the DM RNs?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Clifton. I made the change. PM felt it was better to link than to include all fo the DM fixed issues.

[source]
----
java.lang.NoSuchMethodError:org.keycloak.representations.idm.RoleRepresentation.setScopeParamRequired(Ljava/lang/Boolean;)
----
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add that as a workaround users should add the group in RH-SSO directly rather than using business-central user and group management.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added to the draft.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

Copy link

@romartin romartin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @emmurphy1 , thanks for this work! I think I found an issue here, please check it. Ratherh than this, it looks good to me.

Copy link

@romartin romartin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few more comment from my side @emmurphy1 , thanks!!

== OpenShift
.Nodes and distribution lines do not fully align horizontally [https://issues.jboss.org/browse/JBPM-8555[JBPM-8555]]

Issue: If you drag a node, the align and distribution mechanism correctly displays the alignment lines and also applies the snap-to-line behavior when the mouse moves. However, it is not possible to align the nodes horizontally which means that it is difficult to have the connectors precisely aligned horizontally.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @emmurphy1
Probably I would move the first sentence ("If you drag [...] when the mouse moves") out from the issue section? I mean, that's what the ticket also describes but not sure if it's clear, that's just explaining this functionality, there is no "issue" around this. Anyway just giving my opinion.. up to you how to make it better :)

On the other hand, it is correct than is not possible to align the nodes, but I would probably also add the word "some", meaning that not ALL nodes are not being aligned properly - eg: it is possible to align tasks when same size, but it's hard when mixing tasks with events or gateways... Also the lines that appear, to help on the alignment while dragging, are not well aligned horizontally, I think it's the same bug causing both wrong behaviors....

Thanks!

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated, please review.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it looks good to me, thx 👍


//ifdef::PAM[]
//== Smart Router
.Data output associations do not work correctly when they are declared twice [https://issues.jboss.org/browse/JBPM-8489-[JBPM-8489]]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @emmurphy1
Just added the missing information about this issue, see the updated JBPM-8489
Thanks!

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated, please review.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it looks good to me, thx 👍


== Scenario simulation

.Scenario Designer can not access the parent data object fields [https://issues.jboss.org/browse/DROOLS-4259[DROOLS-4259]]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.


//.With IBM Java, Smart Router with HTTPS enabled causes the `NoSuchAlgorithmException` exception [https://issues.jboss.org/browse/RHPAM-1576[RHPAM-1576]]
.Rule scenarios with maps of simple types fail [https://issues.jboss.org/browse/DROOLS-4243[DROOLS-4243]]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link

@triceo triceo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have made some suggestions.

[id='rn-740-fixed-issues-ref']
= Fixed issues in {PRODUCT} 7.4.0

{PRODUCT} 7.4.0 provides increased stability and fixed issues listed in this section.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"fixes"?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, I think 'fixed issues' is more correct.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do as you will, language is not my forte.



//== Installation

ifdef::PAM[]
== Legacy Test Scenarios tool
== Legacy process designer
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although this information is technically correct, I'm wondering about the wording. "start migrating your processes to the new designer", "Create all new processes in the new process designer."

It may be the accepted way how these disclaimers are written, in which case please disregard my comment, but I do consider this wording very direct, brief, commanding.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, we do mitigate with the caveat 'If you intend to use the new process designer..." And where possible we try to use the imperative (Start migrating... Create... which can seem as you say.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do as you will, language is not my forte.



//== Installation

ifdef::PAM[]
== Legacy Test Scenarios tool
== Legacy process designer
The legacy process designer in {CENTRAL} is deprecated in {PRODUCT} 7.4.0. It will be removed in a future {PRODUCT} release. The legacy process designer will not receive any new enhancements or features. If you intend to use the new process designer, start migrating your processes to the new designer. Create all new processes in the new process designer. For information about migrating to the new designer, see see {URL_MANAGING_PROJECTS}#migrating-from-legacy-designer-proc[_{MANAGING_PROJECTS}_].
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"see see"

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

An installer wizard is provided in the OpenShift Operator for {PRODUCT}. You can use the wizard to deploy a {PRODUCT} environment on {OPENSHIFT} with the Operator.

== Process Instance Migration as a standalone service
Process instance migration is now available as a standalone service containing a user interface and a backend, and packaged as a Thorntail uber-jar. The process instance migration service enables a user to define the migration between two different process definitions, known as a migration plan. The user can apply the migration plan to the running process instances in a specific {KIE_SERVER}.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious about the Thorntail reference. It is factually correct, but isn't there some kind of a productized name for it? Thorntail is an upstream project name.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked and there isn't a productized name that I was able to find.


== Supported components
* {JWS} 5.1.0
* {TOMCAT} 9.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe that this needs changing. We support Tomcat 9 which is part of JWS 5.1.0.
I would stay away from calling out Tomcat 9 independently of JWS 5.1.0.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, why are we even mentioning this, when we reference the supported configurations page on Red Hat website? This information is available there.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First, we had a TAM request that we create a separate Tomcat installation doc:
BXMSDOC-4148
Second, I have had BXMSDOC-2651 on my todo list for a long time, but I do agree with you.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I'm resurrecting the discussion in 4148. Let's keep this as is for now.

@@ -3,164 +3,261 @@

This section lists known issues with {PRODUCT} {PRODUCT_VERSION}.

ifdef::DM[]
COMMENT: Before finalizing, RHPAM or RHDM jiras must be created for each issue. Original jiras are linked in this draft so SMEs can find their issues easily and will be removed before publishing.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we leaving this comment in? Perhaps it's just something I'm not understanding about how the docs are produced.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I've removed it already and just hadn't pushed.

== Google Charts

In {PRODUCT} 7.3.0., the `https://c3js.org/[C3]` chart library replaced the Google Charts library as the default chart library in {CENTRAL}. With {PRODUCT} 7.4.0., Google Charts is no longer available in {CENTRAL}.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

7.3.0. -> 7.3.0
7.4.0. -> 7.4.0

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

* The spaces breadcrumb is hidden [https://issues.jboss.org/browse/RHPAM-2091[RHPAM-2091]]
* Drop-downs in the Security perspective can not be controlled by the keyboard [https://issues.jboss.org/browse/RHPAM-2085[RHPAM-2085]]
* Error for process diagram containing multiple instance user tasks [https://issues.jboss.org/browse/RHPAM-2020[RHPAM-2020]]
* Guided decision able is not getting updated [https://issues.jboss.org/browse/RHPAM-2007[RHPAM-2007]]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

able -> table

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

* Missing translations in the UI [https://issues.jboss.org/browse/RHPAM-1549[RHPAM-1549]]
* Not able to build a project that has a guided scorecard [https://issues.jboss.org/browse/RHPAM-2055[RHPAM-2055]]
* Problem expanding or dragging the right-most column in the data table of a guided rule template [https://issues.jboss.org/browse/RHPAM-1559[RHPAM-1559]]
//* Process diagram is not displayed after importing a project [https://issues.jboss.org/browse/RHPAM-1881[RHPAM-1881]]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this commented out? RHPAM-1881 has been verified for 7.4.0

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uncommented

* Users with the `rest-all` role only are not able to communicate with {CENTRAL} REST endpoints [https://issues.jboss.org/browse/RHPAM-2081[RHPAM-2081]]
* Using the same template key with difference objects and attributes causes an exception when switching to the *Data* tab in a guided rule template [https://issues.jboss.org/browse/RHPAM-1551[RHPAM-1551]]
* The *Task Inbox* column sort order can't be switched for certain columns [https://issues.jboss.org/browse/RHPAM-2032[RHPAM-2032]]
* The *Task List Saved* filter applies different expressions when defining and using [https://issues.jboss.org/browse/RHPAM-1957[RHPAM-1957]]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

*Task List Saved* filter applies -> *Task List* saved filter presents

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Copy link

@sterobin sterobin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@emmurphy1, done. Excellent job on this! I feel like the RN gets tidier and more consistent every release, especially the known and fixed issues. I have quite a few comments, but mostly small fixes and tweaks, and most not necessarily from you. Great work, Emily!

And just a reminder to not forget to expand my "hidden" comments below :)

@@ -18,16 +18,17 @@ include::{enterprise-dir}/release-notes/rn-intro-con.adoc[leveloffset=+1]
include::{enterprise-dir}/release-notes/rn-whats-new-con.adoc[leveloffset=+1]


Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Things note in this PR:

New features: Test scenarios

  • "The test scenario designer displays" > "test scenarios designer"
  • "Test a RuleFlow group." > "a ruleflow group" (normally two words, but problematic because one word in the test scenarios UI, so this is fine one word)

New features: Process designer

  • "There is added functionality to choose" > "You can now choose ..."
  • "There is added support for the following new advanced user task properties:" > "The following new advanced user task properties are supported:"
  • "You can now import processes with a collapsed sub-process." > "subprocess" This comes up several times. I believe from your and my previous discussions, we agreed on one word, no hyphen. I suggest to search all instances of "sub-process(es)" and change to one word. If you've since changed your mind, hyphenated then, but still needs to be consistent.

New features: RH OpenShift

  • "Business Central extensions for OpenShift and OpenShift startup strategy for Decision Server" > In this section the rhpam74-prod.yaml file name seems to be hard coded instead of variablized because it appears the same in the DM RN. So either it's PAM only or it needs to be a variable. @mramendi? ^

Technology preview

  • "administration page which is disabled" > "administration page that is disabled"

Known issues: Business Central

  • "Human task comments are not retained when a process instance is finished" > Missing JIRA link.

Known issues: Process designer

  • "The multiple instance properties of a ..." > Missing JIRA link. Also, swap the expected result and actual result so that expected is first, and apply sentence style capitalization to "Steps to reproduce", "Expected result", "Actual result", etc. These changes are consistent with the other sections.
  • "Data output associations do not work" > Same as above: Swap the result order, and apply sentence style capitalization to each portion).

Known issues: Scenario simulation > Change section title to "Test Scenarios". The term Scenario Simulation is outdated and what is often used upstream as a synonym.

  • "Scenario Designer can not access" > "Test scenarios designer cannot access"
  • "Issue: Scenario Designer can not access" > "Issue: Test scenarios designer cannot access"
  • Same as above: Swap Expected and Actual results so Expected is first, and apply sentence style capitalization to each portion (Steps to reproduce, etc.)
  • "Rule scenarios with maps" > Ditto on swap result order, and capitalization.

After all updated, suggest running quickly through the Known issues sections to confirm consistent sentence style caps for "Steps to reproduce", "Expected result", "Actual result", etc.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mramendi I assumed that you intended the above mentioned OS entry for DM and PAM so used variables in the file. Please confirm.

[id='rn-support-ref']
= Support and compatibility

This section lists supported version updates and {PRODUCT} {PRODUCT_VERSION} deprecated and removed features and components. For a comlete list of supported configurations, see
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"complete list" (typo) Also, it says this section lists both supported and deprecated features and components, but then the "Deprecated components" chapter is listed separately later. So I think we either need to update this description to not mention deprecated features or modify and move that deprecated features chapter into this chapter. I personally like the second option of including that deprecated section here in this chapter.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great idea. I've reworked the section.

@@ -10,15 +10,29 @@ These features are for Technology Preview only. Technology Preview features are
For more information on Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Scope].
====

== High-availability authoring on {EAP} (on premise and with OpenShift)
== High-availability authoring on {EAP} (on premise and with OpenShift)
Configuration of {CENTRAL} for high availability is currently technology preview. Search and messaging technology used to enable search feature is considered an implementation detail. {PRODUCT} may choose to replace that technology in the future while preserving the capability offered.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"is currently a Technology Preview feature." Capped when referring to the proper TP, otherwise lower case. How it stands is probably correct cap wise, but syntactically strange, and the change necessitates the cap. That said, we're still not super consistent about how we refer to TP anyway, but at least trying to improve it here and make it consistent with the boiler plate text for this, such as in the case modeler section.

"detail. That technology may be replaced in {PRODUCT} in the future while the capability offered may be preserved."

I don't really understand this section per se, nor my suggested rewrite to be honest, but we at least need to avoid saying that the "{PRODUCT} may choose", which is what I've tried to do.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing that. What this section was trying to say is that we might replace ElasticSearch with DataGrid but if we do, there will be no loss in functionality. However, that has happened so I will ask if I can just leave it at the first sentence.

ifdef::PAM[]
== Case modeler
Case modeler now provides the option to model a case as a sequence of stages so it is simple to define a case model at high-level. Case modeling supports three types of tasks: human tasks, sub-processes, and sub-cases.
Case modeler now includes the new process designer. It provides the option to model a case as a sequence of stages so it is simple to define a case model at high-level. Case modeling supports three types of tasks: human tasks, sub-processes, and sub-cases.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest "The case modeler in {CENTRAL} now includes ..."

"case model at a high level."

Also, the "sub-processes" here may be an exception to the one-word rule I mentioned earlier, since it might look odd to then say "sub-cases", which is correctly hyphenated. So it's your call whether to leave both hyphenated for aesthetics or to collapse subprocess for consistency throughout.

An installer wizard is provided in the OpenShift Operator for {PRODUCT}. You can use the wizard to deploy a {PRODUCT} environment on {OPENSHIFT} with the Operator.

== Process Instance Migration as a standalone service
Process instance migration is now available as a standalone service containing a user interface and a backend, and packaged as a Thorntail uber-jar. The process instance migration service enables a user to define the migration between two different process definitions, known as a migration plan. The user can apply the migration plan to the running process instances in a specific {KIE_SERVER}.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"and a back end" We really need a more specific term here per IBM, but at a minimum needs to be two words to be correct. And +1 to @triceo's question.

Also, below, suggest "... see the https://github.com/kiegroup/droolsjbpm-integration/tree/master/process-migration-service[Process Instance Migration Service] page in GitHub." That's how we typically refer to upstream repos, plus how this stands is unclear or even incorrect in how it refers to the KIE Group.


== DMN
* DMN large memory allocation bug [https://issues.jboss.org/browse/RHDM-907[RHDM-907]]
* Laptop arrow keys do not move selection through all of the options in a dropdown menu [https://issues.jboss.org/browse/RHDM-912[RHDM-912]]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"drop-down menu"

* Error upgrading from {PRODUCT_DM} 7.2.1 to 7.3.0 using the migration tool `rhdm-7.3.0-update` [https://issues.jboss.org/browse/RHDM-944[RHDM-944]]

== OpenShift
* User password is exposed in the Readiness and Liveness probes [https://issues.jboss.org/browse/RHDM-848[RHDM-848]]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the PAM version of the RN, this is listed under "Business Central" and worded slightly differently, as follows: "User password is exposed in the Readiness probe and Liveness probe" Just for what it's worth. I like the PAM version because it clarifies that they are two probes.

== OpenShift
* User password is exposed in the Readiness and Liveness probes [https://issues.jboss.org/browse/RHDM-848[RHDM-848]]

== PPML
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"== PMML" (typo)


== PPML
* Creation of a container with PMML fails in {KIE_SERVER} [https://issues.jboss.org/browse/RHDM-863[RHDM-863]]
* Creation of a container with PMML fails in SpringBoot [https://issues.jboss.org/browse/RHDM-852[RHDM-852]]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For both bullets, suggest "of a KIE container" for clarity.


== {KIE_SERVER}
* Need an `slf4j` adapter for {KIE_SERVER} with {PRODUCT_DM} 7 [https://issues.jboss.org/browse/RHDM-866[RHDM-866]]
* Remove unnecessary listener from RHDM Kie server distribution for JWS [https://issues.jboss.org/browse/RHDM-859[RHDM-859]]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest "from {KIE_SERVER} distribution"

. Start a process instance with two consecutive human tasks.
. Comment on the first human task.
. Claim, start, and complete the first task.
. Check the log file to confirm that the comments are retained for the completed task.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not log file (here and in 'Excpected' and 'Actual' results below), but rather a Tab in UI, can we refer to it as Comments Tab (of a Human Task)?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done


.If a case task actor is invalid, the resulting BPMN file is also invalid [https://issues.jboss.org/browse/RHPAM-2240[RHPAM-2240]]

Issue: The new process designer sometimes generates an invalid XML file . A user task with an actor assigned is generated as a a `potentialOwner` element in the XSD file.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the white space before the '.' harmless here?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

. Start a process instance with two consecutive human tasks.
. Comment on the first human task.
. Claim, start, and complete the first task.
. Check the log file to confirm that the comments are retained for the completed task.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not log file (here and in 'Excpected' and 'Actual' results below), but rather a Tab in UI, can we refer to it as Comments Tab (of a Human Task)?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed


.If a case task actor is invalid, the resulting BPMN file is also invalid [https://issues.jboss.org/browse/RHPAM-2240[RHPAM-2240]]

Issue: The new process designer sometimes generates an invalid XML file . A user task with an actor assigned is generated as a a `potentialOwner` element in the XSD file.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the white space before the '.' harmless here?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

@@ -1,161 +1,155 @@
[id='rn-whats-new-con']
W[id='rn-whats-new-con']

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is the 'W' intended here?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, fixed.

@emmurphy1 emmurphy1 merged commit fbe48d2 into BXMSDOC-4014-master Jul 10, 2019
emmurphy1 added a commit that referenced this pull request Jul 10, 2019
emmurphy1 added a commit that referenced this pull request Jul 11, 2019
@emmurphy1 emmurphy1 deleted the BXMSDOC-4014-master-final branch January 30, 2020 12:47
emmurphy1 added a commit that referenced this pull request Jan 4, 2022
)

* Startup strategy configuration in OpenShift Operator

* Update doc-content/enterprise-only/openshift/operator-deploy-basic-proc.adoc

Co-authored-by: emmurphy1 <30830712+emmurphy1@users.noreply.github.com>

Co-authored-by: emmurphy1 <30830712+emmurphy1@users.noreply.github.com>

Co-authored-by: emmurphy1 <30830712+emmurphy1@users.noreply.github.com>
emmurphy1 added a commit that referenced this pull request Jan 4, 2022
)

* Startup strategy configuration in OpenShift Operator

* Update doc-content/enterprise-only/openshift/operator-deploy-basic-proc.adoc

Co-authored-by: emmurphy1 <30830712+emmurphy1@users.noreply.github.com>

Co-authored-by: emmurphy1 <30830712+emmurphy1@users.noreply.github.com>

Co-authored-by: emmurphy1 <30830712+emmurphy1@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
8 participants