Top
Top
LibraryEASYProcess Training GuideChapter 1: Starting With EASYProcess
Starting EASYProcess and Enterprise Manager
Source Control Management (SCM)
Enabling Quick Access Menu

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.

Starting EASYProcess

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.


 Source Control Management (SCM)

After we set up multiple environments (DV, QA, PD, etc.), we will set up a SCM system which only allows us to develop in the DV environment, while keeping the QA environment clean from incomplete features. While developing you may break things accidentally or only develop half of a feature. During this time, the feature should not be tested or available to users because it will have behave unexpectedly. For this reason, testers are given access to the QA environment.

This sets up a promotion path so that once an issue or feature is fully developed and the developer has tested it in DV, it is ready to be quality tested or User Acceptance Tested (UAT) in QA. After it is approved by the testers in QA, it is ready to be promoted to Production.

DV, QA and PD are not the only environments that can be set up in the promotion path. The environments can be set up according to the clients needs. One reason for this is several testing groups. There could be two testing environments and each group of testers would take an environment. There may also be a training environment. This would allow new users to be trained on the system without affecting any production data. Another reason would be to have a copy of PD called Pre-Production. These are usually given the same specs as the production server so that stress tests can be performed.

Our SCM compiles all changes into projects. So if the change requested (issue fix or feature) requires multiple webparts or processes, those can be grouped into projects and moved through the promotion path together. This ensures that a feature will not be unstable for the few minutes it takes the developer to promote all the associated webparts and processes. An unstable feature could result if half the feature was promoted at 12:00 and the other half was promoted at 12:30. Any testers using the site during that time would receive unexpected behavior.

If all the environments of the promotion path are already set up, to view the promotion path in EEM, navigate to SCM under the “Team Development” menu.

This will open a screen with 3 panels. At first, all the panels will look pretty empty. EEM needs to be told which computers contain the environments that create the promotion path.

Right click the “Computers” node and click “Attach a Computer”.  Here you can type the computer Name or IP Address.

Now the left panel should display the computers attached and the associated EASYProcess Applications. The middle panel will display the promotion path tree. Each level of this can be clicked on and in the right panel will show the webpart, processes, webpages, etc. that currently are checked out for changes and are sitting in that environment awaiting approval to move to the next step on its way to production.


Enabling Quick Access Menu

Before we begin using EASYProcess, a setting should be turned on to make your development easier. EASYProcess has a feature called “Quick Access (Flyover) Menu”. To enable this feature, once EASYProcess is open, under “Tools” select “Preferences”.

Once inside the “Preferences” window, in the “General” tab, select “Turn On Quick Access (Flyover) Menu” and click “Save”.

Notice this adds two tabs at the right of EASYProcess. Click on them to expand them.

When you have multiple windows open within EASYProcess, they will be shown in windows in this “Windows Preview” tab. This will make it easy to switch between two windows you have open and make development faster.

The other tab, “Recent Items” shows the recent windows you had open. This will help when you begin working on projects to easily move between relevant WebParts and Processes.

Without this Quick Access Menu, you could switch between windows with the “Window” menu. This will allow you to view all open windows and display them in different ways.

If you wish to turn off this feature later, you can do so in the same way you turned it on.


Powered by EASYProcess (© 2019 K-Rise Systems, Inc).