Service Canvas Overview
This is where you provide input parameters for the opened service.
Some areas of this screen are also available for the Process Canvas (like Configuration Settings), but their use in relation to the Service Canvas is explained below.
To your left, you will find:
Configuration Settings: These are separated into different lists.
Configuration → Systems
These are Environment wide variables that can be set up for the system. It is useful for defining a variable used in the system that can easily be changed later. The values of these may change, but the structure of what variables can exist will likely not change.
Configuration → Applications
These are the same as the configuration variables for the system, except the structure can easily be changes as well as the values of those variables. If you were creating a process and were referencing a variable in lots of places, but that value could change in the future, you would add one of these configuration variables and reference it for an easy change in the future.
EPUser → Entity
This allows quick access to the current logged in user's EPUser entity properties.
The service designer section in the middle has two major parts:
Service Tree: The top half of the service designer lists parameters for the selected service that you need to specify so it could run properly. Some of the parameters may have default values filled in and some may not. Some parameters may be required. Some services could accept complex inputs and others could be very simple. Further documentation is available for specific services if it is not clear how it functions or what inputs are needed.
Value Box: The bottom half of the service is used to specify a value for the parameter selected above. Value can be typed in, or could be dragged and dropped from Configuration Settings on left or Recommended Values to the right.
To your right, you will find:
Properties that exist for the service. Not all of these are editable, but can be useful in some scenarios.
This area displays the projected output nodes from services preceding the selected one on the canvas. It also suggests other relevant values that may be applicable to the selected parameter. Sometimes, depending on the service, it may provide a list of accepted values for the parameter.
This tab is used to view and edit the notes left on services. Once a note exists for a service it displays with a note icon on the Process Canvas to alert future developers that there is a note to read.
The Query Builder is a tool that is available in various areas in EASYProcess such as process services (like Inquire or RunQuery) and the EASYProcess RunSQL tool. This tool allows a SQL query to be using built and represented visually.
From the list of Configuration on the right, find and double-click (or drag and drop) “DbName” under the JDEData profile. If your JDEDbType and JDEDbConnectionString were correct in the database canvas, all the tables your JDE data library will be populated. Refer to the image below.
Find the desired table in the list, highlight it and double-click (or drag and drop) to add the table to the query builder canvas. Notice that the query that will be used is automatically typed in for you in the bottom left corner.
You can do this for multiple tables and then join them by dragging a column from one table to the column it maps to in the joined table. As you do this, the exact query used is typed in for you in the bottom left corner.
Click on “Use this Query” button. You will be redirected to the Service you orginated from which now contains the query you created with the Query Builder tool.
If you wanted to go back into the Query Builder screen, you would have to select the text you want to feed into the query builder for it to display just as it did before you clicked the “Use this Query” button. This is because when queries get to be complex you may want the query builder to only work on a portion of your query, like a subquery or the first half of a union. This gives the developer control over what is represented visually on the Query Builder canvas.
Service Level Value Transformations
There are a few ways to apply value transformations, but one of them can be performed on the service canvas.
Value Transformations can be performed at the service level. This exists for all services, but is most commonly used for services that query a database, such as Inquire or RunQuery.
The Service level Value Transformation page is available at the right side of the service canvas. Notice there are two tabs: Service and Value Transformation.
Here is the screen for the value transformation tab.
Service Output: The service’s output is listed on the left. Selecting one will do two things: filter the “Existing Value Transformations” list and autofill the “New Output” textbox in the “Add New Value Transformations” section.
Add New Value Transformations: After either typing in an output or selecting one from the Service Output panel, the “New Output” text box will be filled with an output. Click “Add New Output” and it will be added to the drop down list next to “Select Output”.
With an output selected in the drop down list next to “Select Output”, you can select a rule to perform on that output and click the “Add” button above the list section of Existing Value Transformations.
Existing Value Transformations: All the active value transformations for the service will be listed here. This list could be filtered to only show the value transformations for a particular output by selecting an output from the Service Output panel. To unfilter this list, click the “Show All” button and all existing value transformations will be shown. From here entries can be deleted or moved up or down to edit the order in which the value transformations will run.
Creating Value Transformation
Here is a diagram that illustrates the steps of creating a value transformation.
- Select the Output you want to perform the value transformation on. This will auto-populate the “New Output” text box.
- Click “Add New Output”. This will select the output in the “Select Output” drop down.
- Select a rule. This is the transformation that will be performed.
- Click the “Add” button and the new entry will be added to the list section below.
The value transformation occurs at the service, so it affects the output of the service. Here is the output before and after the transformation was added.
Notice the ALEFTB output is returned in JDEDate
The ALEFTB output is in a regular date format after applying the “ConvertFromJDEDate” rule.