Skip to main content

Checklist - Fix a Rules Manager Action


This is for the Test instance

This script was created based on Max-1937, fix a CRON task, but since testing is so hard, I copy the code to a test action, fix and test, and then apply that fix to the actual CRON task. 

  • In Jira – use the (Create branch) function to create a branch
  • In Rules Manager Studio switch to the RulesManager Developer perspective
  • Press the 
    Create Connection
  • Switch to the Git perspective
    • Expand the repository you are working in (in this case the one starting trm.rm.https.sdt-max1-s…)
    • Expand the branches, local, and remote tracking
    • Double click the branch you are working on.
      • If it’s not in local, double click the branch in remote tracking. it will offer to Check out as New Local Branch, when doing this it will create a branch on your local repository.
    • Switch back to the Rules Manager Developer perspective

: make your code changes (in my case to the test action)

  • For each xml file you changed
    • Right-click that file and press commit
  • Highlight the connection and then click the 
     (commits back to server) button. 
    *** Michelle is this needed? or did commiting the file directly do this ***
  • Highlight the connection and then click the 
     (request server to refresh server from filesystem) button
  • Navigate to Maximo https://sdt-max1-s.saccounty.net:9443/maximo/
  • Execute the action
  • Don't forget to check the log
    • \\sdt-max1-s\IBM_sdt_max1\maximologs\maximo\logs\sdt-max1-s_MXUI1_RulesManager.log


If it looks like your changes are working, then the changes need to be propagated to the rest of the environment

  • Start Rules manager studio
  • (Computer 1) If you're not already connected, press the 
     (Create Connection) button
  • Confirm your fix is in place in the test action
  • Apply changes to your actual code
    • In the Server Explorer, for each file that was changed, right click the file you just saved, pick commit
    • click the 
       (Commit back to the server changes made to rule file) -
       *** Hmm, is this needed ***
    • On the Server Explorer toolbar click the 
      (request server to refresh rules from file system to system memory) button


  • (Computer 2) Press the 
     (Create Connection) button
  • Apply your changes to the test action
  • Apply changes to your actual code
    • In the Server Explorer, for each file that was changed, right click the file you just saved, pick commit
    • click the 
      (Commit back to the server changes made to rule file) - *** Hmm, is this needed ***
    • On the Server Explorer toolbar click the 
      (request server to refresh rules from file system to system memory) button


  • (Computer 3) Press the 
     (Create Connection ) button
  • Apply your changes to the test action
  • Apply changes to your actual code
    • In the Server Explorer, for each file that was changed, right click the file you just saved, pick commit
    • click the 
      (Commit back to the server changes made to rule file) - *** Hmm, is this needed ***
    • On the Server Explorer toolbar click the 
      (request server to refresh rules from file system to system memory) button


  • (Computer 4) Press the 
     (Create Connection) button
  • Apply your changes to the test action
  • Apply changes to your actual code
    • In the Server Explorer, for each file that was changed, right click the file you just saved, pick commit
    • click the 
      (Commit back to the server changes made to rule file) - *** Hmm, is this needed ***
    • On the Server Explorer toolbar click the 
      (request server to refresh rules from file system to system memory) button
  • (Source Control)
    • Switch to the GIT perspective
    • In the Git Repositories window, expand the repository (trm.rm.https.sdt-max1-s.saccounty.net:9443….), branches, local, (remote tracking) and (working tree)
    • In the Git Staging window, the files you changed should appear in the unstaged changes list. Click those and press to add it to the Staged Changes window
    • (Note: if you double click a file in the Staged Changes window, the Compare window will show a before and after window)
    • Enter a commit message
    • Press commit and push … (or just Commit, if you will be making other changes as part of this same maximo ticket)
    • Switch to BitBucket
    • Create a Pull Request
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.