Looking for Additional Feeback on Valley Health Findings...

Hans Mueller

Hi all - 

Per our call today, I am posting the findings from Jeff and his team at Valley Health.  We would love the other customers (and Infor team members) to provide additional feedback on any of the items below if applicable, and we will discuss further on our next call.

Note - there were some screenshots that were included, so I am also attaching a PDF of the entire email with screenshots included for reference.

Below are my notes from an hour or so of on-and-off testing this afternoon. Please let me know if you have any questions.

1. [Problem] You can’t tag process configurations (Process Server Administrator > System Configuration)

1. 1. Our interfaces have a variety of configurations and in each environment the values could be different (usually emails or lookback periods), but most are the same and we still want to make sure we copy all of the configuration settings defined so that they can be changed in the next environment. This means these would have to be done manually or with ISD.
   2. [Request] What I would prefer is that you can choose which tagged items overwrite the target and which don’t. If I’m migrating an interface from TST to PRD for the first time then I want to take the TST interface configuration with it and then I can update it for PRD. If the configuration already exists in PRD then it can be skipped.

2. [Problem] You can’t tag File Channels.

1. 1. These are a part of most of our interfaces. There are frequently one or more File Channel or File Channel Receivers set up for an interface to kick off processes when files arrive

3. [Problem] Error occurred when the compare option was selected on the deploy local package screen.

1. 1. I believe this is the same one already reported by Zach or Harry. I clicked Continue Deployment and it continued.
   2. I do see that in Chapter 4 it mentions that the compare report is not supported in FSM and HRT. This is why I tagged it as a problem. It would be good to be able to compare the package to the target environment before completing the deployment. The Change Management within the Configuration Console lets you do that.
   3. [Question] Is the compare report going to be fixed to work with FSM and HRT?
   4. [Question] Is there any way to export the package so it can reviewed locally (on my computer)?
   5. Error Screenshot

4. [Problem] Package didn’t deploy all of my configurations even though it reports the deployment as successful.
Package ID: 1abf3df5-4db0-4831-9e14-ead424fad144

1. 1. The Configuration Console JOSH TEST BUNDLE contains 4 configurations.
      • VMCFTEHistory, VMCRelationshipStatusHistory (invalid), VMCRelationshipStatusHistory  (inactive) and VMCTestConfiguration.
      • The inactive one was one I deleted previously, but it hung around in the bundle so I left it there for the test.
      • The one is showing as invalid was active until I deleted the other two because there is a dependency between them.
      • I created a Local Package in Configuration Management and then deleted those 3 configurations out of DEV.
      • Then I deployed the package back to DEV.
      • It completed and says successful but there are no configurations created: active, inactive, or invalid.

5. [Needs Work] The documentation listing what can be imported needs work. I found I can’t tag PfiConfigurationProperty, PfiChannel, PfiReceiver, and others by trial and error. It would be nice to have a complete list of what can and can’t be tagged.

1. 1. [Request] Under Administration Console > Database >  Copy Action List there is a list of every business class and what gets copied during a refresh. It’d be nice to have something similar for this: list out every business class and whether it can be tagged.
   2. Under Landmark Resource is a generic area/name and Description is a business class.
      
      Then under FSM and HRT neither the Resource or the Description column lists a business class.
   3. [Request] It would be good to know what business classes also drag in other business classes. For example when I tagged a PfiFlowDefinition record it brought in the PfiFlowVersion records. Understandable, but if I migrate an IPD with Infor Process Designer I don’t get all versions so that’s not something I’d expect to happen, and depending on what’s in the older versions I might not want that to happen.

6. [Oddity] Confirmation buttons are swapped from the rest of Infor. Typically the OK/Yes button is on the right and the Cancel is on the left. Configuration Management’s buttons are backwards.

1. 1. I never realized how much muscle memory I had for clicking OK or Cancel on Infor confirmation dialogs until the buttons were swapped in Configuration Management.

7. [Oddity] You can’t tag individual configuration. You have to tag configurations with Configuration Console tags, then create Configuration Console bundles, then use Tag for Export on the bundle.

8. [Oddity] The error logs download as .bin files but the run time logs download as .log files.

9. [Request] It’d be good to have a revert option. That is available with Configuration Console snapshots. You can roll back a whole snapshot.

10. [Good] You can tag Process and Service Definitions.

[11. Good] Tagging a User Defined Process gets all of the versions underneath it.

1. 1. I tagged GHR-9 and when it imported it brought in all 66 flow versions under it.

12. [Good] I was able to deploy a package back to the same environment and restore deleted configurations.

[View:/cfs-file/__key/communityserver-discussions-components-files/767/Valley-Medical-Configuration-Management-Findings.pdf:320:240]

cleverly

Thanks to Valley Medical for creating this list and to Hans for sharing it (I think Delmar deserves credit for suggesting it on the call).  Very helpful! 

Here are a few comments and thoughts from AgReserves on these items:

#1: It would be slick if there was a way to mark (I hesitate to use the work "tag" ;-) any tagged item as either "create only" (create or ignore) or "create and update" (insert or replace).  We definitely would like a way to make sure we don't miss anything when initially going to a new environment, but also—like I imagine most customers will—have a few that should always differ.

#2: Many of our interfaces involve file channels & receivers too, so being able to tag and move them will be important long term.

#3: We talked about this on the call last week, so I won't comment further other than to echo the 3rd subquestion: is there a way to download and review the content of a package locally (like you could with a configuration console bundle, for instance)?

#4: As mentioned on the call, for tagged config console bundles, it would be nice to have an option to go ahead and validate them automatically and then to (optionally) have them be imported if validation was successful.

#5: Agreed that the documentation could be improved to make it clearer what can be tagged.

#6: Yes! Please fix! 

#7: The documentation would benefit from a discussion of Configuration Console tags and how they differ and how they interact with Business Object tags.

#8: nothing to add.

#9: A revert option would be very nice.

#10: nothing to add.

#11: We would consider this specific example (of pulling in all versions of a flow) a problem and not a good thing.   

#12: We haven't tried that yet, but that's great that it works.