Starting EASYProcess and Enterprise Manager
EASYProcess is our Application Development Platform which is used to develop all K-Rise solutions. It is the tool with which complex web portal applications can be created. Each time an instance of EASYProcess is installed, another tool, EASYProcess Enterprise Manager (EEM) is also installed. This manages the different installations on the server and allows Source Control Management (SCM) to be set up.
Once both EASYProcess and EASYProcess Enterprise Manager are installed, you can open them to begin creating. To start, open either EEM or EASYProcess. The one you need depends on how many environments (Ex: Development, QA Testing, Production, etc) are kept on the server. If very many exist, it may be easier to just open EEM and from there choose to open a specific environment.
When opening either EASYProcess or EEM, make sure you are running it as an administrator. They may not have the proper permissions to run if this is not selected. You can right-click and select “Open as Administrator” or you can permanently set the shortcut to open as an administrator by right-clicking the shortcut and selecting “Properties”. From there, click on the “Shortcut” tab and click “Advanced” for “Advanced Properties”.
Starting EASYProcess Enterprise Manager (EEM)
If you open from EEM, the home screen will look something like this:
This is the home screen of EASYProcess Enterprise Manager. To return to here, you could navigate to “EASYProcess Installations” under the “Action” menu.
This is one of the most useful screens that we will use within EEM because it allows you to view all installations and read information about each install. From here, you can also right-click an environment and click “Start EASYProcess”.
You will notice that in the screenshot, we right-clicked the “EASYCommerce” Application under the “MyOrders_QA” environment. The application and environment names will vary for client to client, so the naming of these may change, but the idea is the same. You could right-click the environment level and open EASYProcess from there, but the EASYProcess that opens would then prompt you to select the Application.
In this example, EASYCommerce is the name of the application, so this is the one we want to open. Your application could be given any name depending on its use (uses for EASYProcess vary), but each application has a corresponding “Base” application as well. The “Base” application should not be opened or edited. The EASYCommerce application is where you would develop to make changes that would appear on your EASYCommerce site. Base allows you do that and use EASYProcess.
If you started by opening an application level EASYProcess shortcut from the desktop, this is the first screen you would see. On the left-hand side, you have some buttons to take you to some most-used areas of EASYProcess. On the right-hand side, you have a screen with your recently used items and some data about when you last accessed them. Once you are more familiar with EASYProcess, you will use more of these buttons, but the two most important are “Work with Webparts” and “Work with Processes”.
WebParts and Processes
Webparts have to do with front-end, UI changes. Processes have to do with back-end logic or algorithmic changes. For instance, if I wanted a page with a drop down list and a button to save the user’s selection to a database, the drop down list and the button would be created through a webpart. However, the logic to decide what values populate the drop down and how and what to save from the user’s selection would be done in a process. We will explain both concepts must further, but here is a glimpse into both of them.
This is an example of a small webpart:
This an example of a small process. You will notice it resembles a flowchart. This is because it follows the flowchart concept to help visually explain the process and various cases of possible behavior.