1

Plug-in assemblies

From Resco's Wiki
Jump to navigation Jump to search
Business logic
Client-side

Server-side

This document is a brief summary of plug-in assemblies in Resco Cloud and their implementation to the processes (workflows).

Getting started

Plug-in assemblies allow you to run custom C# code on the Resco Cloud as part of the Processes. Plugins can run periodically as jobs or be triggered as workflows. It should solve the limitations of the no-coding editor of processes. There are the typical use cases:

  • complex logic of process
  • communication with some third party system
  • etc.

In Resco Cloud, you can manage plugins using the Admin Console.

Creating a plug-in assembly

  1. Download Resco SDK.
    Sample projects are part of the RescoCRM.Plugin.SDK.zip file.
  2. Create a new project as a Class Library (.NET Framework 4.6.2).
  3. Add a reference to the downloaded XRMServer.Core.dll.
    Creating a plug-in assembly: Add reference to dll
    Creating a plug-in assembly: Add reference to dll 2
  4. Implement the PluginBase interface.
    Creating a plug-in assembly: PluginBase interface

Return value of plugin

You can define the return value of your plugin.

Implement the IPluginReturnValue interface to the code (e.g. string):

Plug-in assemblies: Return value of plugin: IPluginReturnValue

These are the allowed return types: It should be possible to create a variable of this type in Processes editor.

Plug-in assemblies: Return value of plugin: Allowed return type

Input values of plugin

You can define the input values of your plugin.

Plug-in assemblies: Input values of plugin: Input values

The name of the PluginInputParameter (MyPluginInput in the example), will be visible in the Processes editor.

Plug-in assemblies: Input values of plugin: MyPluginInput

Logs

context.AppendLogLine("Contacts with specified account id '{0}' cannot be found!", accountId);

Logs are saved and visible in the Admin Console under Processes Center > Logs.

Cancel the workflow execution

context.AppendLogLine("Contacts with specified account id '{0}' cannot be found!", accountId);
return PluginResult.Failed;

Examples

Fetch

Plug-in assemblies: Cancel the workflow execution: Example fetch

Create

Plug-in assemblies: Cancel the workflow execution: Example create

Update

Plug-in assemblies: Cancel the workflow execution: Example update

Delete

Plug-in assemblies: Cancel the workflow execution: Example delete

Adding plug-in assembly to the Resco Cloud

In the development tool:

  1. Build the solution.
    Adding plug-in assembly to the Resco Cloud: Build solution
  2. Create the zip file with the dll file.
    Adding plug-in assembly to the Resco Cloud: Create zip

In the Admin Console:

  1. Go to Processes Center > Plug-in Assemblies.
  2. Click New, then click Browse and upload the zip file.

The plugin is loaded and the return type and input parameters listed below (if implemented).

Adding plug-in assembly to the Resco Cloud: Plugin successfully loaded

Note If you don't see the plugin in the list, log out and then log back in.

Executing plugins

  1. In the Admin Console, go to Processes Center > Processes.
  2. Click New to create a new process.
  3. As Category, select Workflow or Job.
  4. If your plugin has a return value, it is necessary to add the variable of this type to the editor, then you are able to select the plugin.

Plug-in assemblies: Executing plugins: Process using the demo plugin

Process logs

Whenever a process is executed, the run generates a log file entry. To access the logs, go to Processes Center > Logs.

Plug-in assemblies: Process log

Exporting plugins

If you need to transfer a plugin from one organization to another:

  1. In the Admin Console, go to Settings > Organization
  2. Click Export Organization and select Custom.
  3. Select Plug-ins and click Export.

You can then import the files to the other organization using the Import Organization button.

Alternatively, you can export/import plugins between connected environments.

Exception: There is already an open DataReader

When you fetch data but don't use the result, you can encounter the exception System.InvalidOperationException: There is already an open DataReader associated with this Command which must be closed first. To avoid this problem, make sure that all fetch results are used.




Was this information helpful? How can we improve?