Customizing the Case Management Accelerator in live edit mode using RADJAD
By:
Last updated:
12:38am Oct 19, 2017

When customizing appdev applications like the Case Management Accelerator - it is best to use live editing mode to change files. This allows you to use external tools like eclipse to edit your HTML and JS code. This also avoids the need to deploy the app to the appdev console until you are ready to test externally.

To use RADJAD to edit the Case Manager App do the following:

  1. You need to be on the same machine as the BPM engine - normally you would use the BPM Developer Installation on your laptop
  2. Extract the product CaseManagementApp.app.zip from edelivery.tibco.com to a folder on your machine - example: c:\myapps
  3. Extract CaseManager.app.zip to c:\myapps
  4. Rename the CaseManager.app folder created to CaseManager
  5. Login to appdev portal using your browser: http://localhost:8080/apps (this will create the active bpm session in the browser required to use radjad)
  6. Now to access your app, open a new tab and use this "radjad" URL:
http://localhost:8080/apps/CaseManager/index.html?bpm_app_rad_enable=true&bpm_app_rad_artifacts_url=file:///c:/myapps

In effect, appdev is now using your local source copy of the app, rather than pulling it from the BPM repository. You can now literally edit files live in c:\myapps\CaseManager and just refresh the browser to see changes.

Note that any dependencies you reference must also be extracted to the c:\myapps folder - appdev will assume everything is in that folder. Using RADJAD will save lots of time when creating/editing appdev apps. To turn off radjad just use ?bpm_app_rad_enable=false on the URL. It only effects your browser session, so restarting the browser will also turn off radjad.

Remark: If you get problems be sure to check the browser console - if it cant find a file under c:\myapps you will likely see an error in the console

Hints: If your not using tibco-admin for radjad - the user needs the Edit Application System action. You can get this by

  • configuring the org model to give the user this (normally via privilege assignment from group/position membership) more Details here 


     

  • or just add the user to the Org Model (v0) System Administrator group