On this screen, XML files are displayed, arranged by type. These can be filtered by file name and type. Deleting XML files is also possible, in such a case the database record of the selected file is set to deleted, and it gets physically deleted when the files are saved into the file system.
Upon clicking on the edit icon, the content of the selected XML file opens, allowing manually editing.
XML editor functions
- search in text
- syntax check (against XSD)
Database operations (SQL profiler)
This interface is for monitoring database operations running in the system. A list of database queries run by the system between start and finish is displayed in the top panel. The lower panel shows the details of the selected command.
- Command: the text of the SQL statement is filtered
- MIN 1 MP: queries that ran for a minimum of 1 second are filtered
- MIN 2 MP: queries that ran for a minimum of 2 seconds are filtered
- Start: start monitoring
- Stop: stop monitoring
- Clear: clear list
- Excel Export: the list of commands is exported into an Excel file
This screen shows the list of errors that occurred in the Effector system. When searching by reference number, the root cause and place of the error in question can be looked up. Filtering for time range and specific error message is also an option.
The database objects used by Effector are listed on the left-hand panel. Filtering is possible by:
- type (scalar function, stored procedure, trigger, table, view)
The right-hand panel displays the definition and content of tables (if a table type of object is selected on the left-hand side), or the definition of other objects.
Obsolete database objects
With this function, database objects that are not referenced in XML files or other database objects in use can be listed. By clicking on the “Search…” button, these will be displayed on the left-hand panel, while the right-hand panel will show the definition of such objects. By clicking on the “Recycle bin” button, these objects can be set apart, and they can be permanently removed from the database by clicking on the “Empty recycle bin (Delete permanently!)” button. Placing objects into the recycle bin is practically a modification in the file name, that is, the system adds a specific prefix ($$EFF_DBCTRASH$$) to the name of the database objects to be deleted. By clicking on the “Restore” button, objects placed in the recycle bin can be restored to their original place. The name, type and status of individual objects are displayed in a grid.
In database job, the function does not examine if a given object is referenced. Testing the system for errors that might arise from purging is advisable after each permanent delete.
Active database objects
On this tab, the list of referenced database objects is accessible, while the right-hand panel displays the XML files the database object selected on the left-hand side is referenced in. In addition, it shows the definition (or the table content) of the object, similarly to the “Database objects” screen.
This interface displays the obsolete XML files. The list shows the name, type and status of such files. The content of files can be viewed by clicking on their name.
Selected files can be discarded by clicking on the “Recycle bin” button. In such cases, the files in the database are marked as “In recycle bin”. By clicking on the “Empty recycle bin (Delete permanently!)” button, the status of these files will change to “Deleted”. The XML files with “Deleted” status will be physically deleted upon being saving into the file system. This process cannot be reversed, unless there is a restore point where the file in question is not yet deleted. If the system is reverted to a restore point, the files should be saved in the file system. By clicking on the “Restore” button, files placed in the recycle bin can be restored to their original status.
On the “Active XML files” tab, the list of files with at least one reference is displayed.
To give Effector a unique appearance with a tailor-made color scheme, so-called skins can be generated.
The ‘Skins’ tab shows the available skins. By clicking on the “Details” link, the details of the skin appear. The left-hand panel shows the styles, while the right-hand panel features their style elements.
After editing and clicking on the “Apply” button (and as soon as Effector is automatically reloaded), the skin can be set as the current appearance.
The left-hand panel features a “Colors” tab featuring the skin’s own customizable color palette items.
Generating a unique style is also an option accessible on the ‘CSS’ tab.
The skin editor also offers a chance to limit the skins available for users in their user profile. These are the so-called active skins which can be changed by clicking on the Effector logo. Skins made inactive can be managed by authorized users only.
In addition to available skin elements, additional ones may be generated by clicking on the “‘New” button or by copying an existing skin (using the “Make a copy” button).
Obsolete skins can be easily deleted by clicking on the “Delete” button.
The other, “Palettes” tab of the Skin editor screen offers independent color palettes that remain unchanged during the modification of individual skins. Currently these can be edited in JSON file format.
Obsolete palettes can be easily deleted using the “Delete” button.
In case of both the “Skins” and “Palettes”, export and import is possible in JSON format.
System skins/palettes and default skins/palettes are protected, that is, they cannot be copied or modified. When needed, they can be edited by copying.
It is the list of icons available in Effector. Since their definition is text-based, their color and size can be adjusted arbitrarily in their place of reference (typically an information card).
Use (e.g. calendar icon, color: blue, size: 24px):
<i class=”efi-calendar” style=”font-size:24px;color:#0000ff;”></i>