eSeaGrant features a built-in versioning system for ensuring that all users access only the most recent version.
To version an eSeaGrant FMP interface:
Panel |
---|
borderColor | #CCCCCC |
---|
bgColor | #FFFFFF |
---|
borderWidth | 1 |
---|
borderStyle | solid |
---|
|
As Super-Admin, go to the 'FMP Versioning' layout of the interface you wish to version, and click 'Version'. Upon clicking this button,...
- A copy of the FMP interface being versioned is saved to the same folder as the original, using the following naming convention: prgm_prefix_<"PM" or "RFP">_<current date>.fp7 (e.g. "MITSG_RFP_13_June_2014.fp7")
- The new copy is uploaded to the server, into the eSG system folder 'FMP_versions'.
- The database is updated to reflect the new FMP version.
It's recommended that old versions be either deleted or moved to an archive. - If FMP interfaces are being shared via FMP Server, users will simply access the newest available version.
- Otherwise, users will be prompted to download the new version when attempting to open an old version.
|
Section |
---|
Versioning Local Copies
Versioning New Releases
If your program IS NOT hosting interfaces via FMP Server:
- Download new release.
- Change name of downloaded file to the name of your current local copy, and open it.
- Update configuration scripts.
- Apply any necessary program-specific edits to the layouts
- Version it via the FMP Versioning layout, as described above.
* Users will be prompted to download the new version the next time they open their RFP FMP interface.
If your program IS hosting interfaces via FMP Server:
- Open it
- Apply any necessary program-specific edits to the layouts
- Version it via the FMP Versioning layout, as described above.
- Replace the RFP FMP interface that's currently being hosted by FMP Server with the new one.
* The new version will be available to users the next time they go to select a shared RFP FMP interface to open.