7/4/2025 5:33:23 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
|
|
|
|
Is there a deployment script hook we can append to?
Posted: 28 Aug 09 12:23 PM
|
I'm looking for a way to add a VFS specific script to the deployment such that during or just after the deployment specific information or processes can be ADDED TO the deployment.
For example creating of a deployment info block accessable from the splash screen would be easy to add. The script could then append deployment date, deployment user, deployment VFS Source Machine, deployment VFS Source path, etc
With 200+remotes this information is needed, for phone support (versioning - you can't always push updates to everyone as simply as it appears when your international), as well as other updates/changes.
A client Side hook on the ServerHost portal restore would also be nice to manage client side processes that can't be done as a remotetask. We've run into several of these, for example: no controls exist for stopping serverhost nor can you control when a deployment is installed after sync downloads and marks it as ready to load, so if you need to run a process to update a file that serverhost is using (in program files), you have a problem. We had to push the dll out in a remotetask. Validate it was installed by script that taskkilled serverhost in a second remotetask and then push the portal.
|
|
|
|
Re: Is there a deployment script hook we can append to?
Posted: 31 Aug 09 10:53 AM
|
You can create custom deployment actions by implementing IDeploymentActionProvider (IIRC located in Sage.Platform.WebPortal.Design.dll). In your class that implements IDeploymentActionProvider you'll have access to BeforeDeployment, AfterDeployment (both give you a reference to the PortalApplication), a RunOnBackgroundBuilds property and a GetDeployableItems method where you can write out a file containing the details you mention to the deployment directory.
Once you create your DLL, you just plug it into the deployment by selecting a deployment in the tree and then open the DeploymentActionTypes collection. Add your DLL to that collection and that is it, you've now added your own action to the deployment where you can do whatever you wish.
Is that what you were after? |
|
|
| |
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|