-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
2fa800c
commit 4e48b05
Showing
1 changed file
with
31 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# Process.js Extensions - CRM 2013-D365 Custom Actions | ||
[![download](https://user-images.githubusercontent.com/14048382/27844360-c7ea9670-6174-11e7-8658-80d356c1ba8f.png)](https://github.com/PaulNieuwelaar/processjsext/raw/master/ProcessJSExtensions_2_0_0_0.zip) (v2.0) | ||
|
||
This solution includes a bunch of sample Actions, which replicate some of the standard SDK messages, allowing you to call these easily from Process.js. The actual Actions are just wrappers for the real logic, which is all implemented in plugins (source code available). Check the Actions for the input and output parameters of each, and then call these actions using Process.js to try them out. | ||
|
||
Check out [Process.js 2.0](https://github.com/PaulNieuwelaar/processjs) for examples on how to call these Actions (there's an example for "Retrieve"). You don't NEED Process.js to install this solution, so if you want to use something else to call the Actions, like the new WebApi (shudder), then you can still use these Actions without Process.js. | ||
|
||
These Actions were mostly just created to test out the Entity and EntityCollection parameters I've recently added to v2 of Process.js, but since they might be useful to others, I'm releasing them here as an extra add-on. | ||
|
||
Actions included are: | ||
* Associate | ||
* Create | ||
* CreateMultiple (wanted to test EntityCollection input) | ||
* Delete | ||
* Disassociate | ||
* Retrieve | ||
* RetrieveMultiple | ||
* SetState | ||
* Update | ||
* UpdateMultiple | ||
|
||
The logical names to use when calling the actions are just "mag_" plus whatever above. | ||
|
||
Check the actual process for more info about what input/output parameters are required. | ||
|
||
Each action includes a custom plugin with a plugin step registered against the action to perform all the logic, e.g. getting the input params, processing the request, and setting the output params. | ||
|
||
Note that using actions to do, for example, a Create request, is probably a bit slower than doing a Create request purely through JavaScript (using SOAP or WebApi), since it's making a direct call to the CRM web service instead of calling an action which then executes the action request. However I haven't noticed any significant delays. And you can just display a nice [Notify.js](https://github.com/PaulNieuwelaar/notifyjs) spinner while it's processing. :) | ||
|
||
Created by [Paul Nieuwelaar](http://paulnieuwelaar.wordpress.com) - [@paulnz1](https://twitter.com/paulnz1) | ||
Sponsored by [Magnetism Solutions - Dynamics CRM Specialists](http://www.magnetismsolutions.com) |