Devtools allows access for CSA accounts to some additional background functionality. This will be a quick rundown of all commonly used parts of the tool. There are other relatively useful grids that are not mentioned in this article, like Dashboards, Custom queries, etc. Some are handy, some less so, some require database access anyhow. It all depends on one's workflow.
Caches (https://ims-production.apps.cenosco.local/#devtools/cache)
Working with this section requires care because clicks will lead to immediate action. By now most of the clicks will provide some feedback in the top right-hand angle of the page.
- Application settings - reloads changes to hierarchy, spec configuration, ECH templates etc.
- Regenerate all thumbnails - this can be very tasking on the server so probably should not be run during the working hours. It is used to regenerate thumbnails for attachment images.
- Regenerate only thumbnails that are not filled - similar as above but should only fill in those that do not exist. Both of these are not used very often, maybe for some attachment related troubleshooting.
- Application MetaData (includes: CategoryList) - this will be mostly useful to make sure any newly created CQT views are recognized for Custom queries.
Mails (https://ims-production.apps.cenosco.local/#devtools/sendmail)
This tool is used to send test emails to verify recurring issues with sending emails from the dataservice. If emails are being sent that should confirm that the dataservice email configuration and the email server do not have issues.
Security/Rights (https://ims-production.apps.cenosco.local/#devtools/security)
This tab lists Right/Privileges which basically define which role is allowed to do what. There are exceptions to these rules but generally almost everything is covered with this.
This matter is too complex for purposes of this article so is only mentioned briefly.
Roles (https://ims-production.apps.cenosco.local/#devtools/roles)
Roles are worth checking at times, especially important are the Expired date, Sequence and the Bitmask, which is not included here.
Sequence 20 means that the role is disabled.
Database settings (https://ims-production.apps.cenosco.local/#devtools/databasesettings)
I will often use this list to quickly check for the statistics execution log. When statistics are not running on the site many strange issues occur with data shown in the grids.
The database settings work in conjunction with application settings and are different in that database settings are never shown to the user.
Methodology bitmask update tool (https://ims-production.apps.cenosco.local/#devtools/methodology)
This tool is used to update the bitmask in a trackable fashion as event history is left behind to show who and when was making the changes.
- This tool has many limitations, the "Clear all filters" button is your friend if you can't get it to show what is expected.
- Most useful are the range filters into which Equipment and Floc names can be pasted, but make sure to always check the counts of entities you are expecting as the name does not have to be unique.
- The pin function might not work as expected, use it with caution.
- To subtract bitmask (also referred to as demotion, as in demote and promote) input a negative value. Subtracting should take care of schedules, components and everything else under said Floc/Equipment.
- Equipment may need to be demoted before the Floc is allowed to be demoted.
- Do not expect meaningful feedback from the tool, you may need to refresh the page to see what you expected to see.
- Note that IMS may determine that more bitmask needs to be added than what you specified. For example, adding 1 will probably add 513 if 512 is not already part of the bitmask. The same goes for subtraction.
- Bitmask updates appear to be limited to 200 in one go, that's the maximum number of entities that can be shown per page.
Hard disk tool (https://ims-production.apps.cenosco.local/#devtools/hdtool)
This tool is most often used to grab the trace logs from the server, but it can also be used to get the configuration files, at least those that are currently supported by the tool.
Take care that when looking at trace logs sometimes there may be multiple files for the same date, but also some logs for the current date may end up in the file for the previous date.
Failed Workflows (https://ims-production.apps.cenosco.local/#devtools/failedworkflows)
This list shows logged error that arise from Workflow failures. This information can be rather cryptic at times to understand.
The information provided is more detail than what is found in the trace log. These two logs should complement each other.
Next Schedule List (https://ims-production.apps.cenosco.local/#devtools/wfscheduler)
This list can be used to troubleshoot the email scheduler which is used by custom queries (maybe also elsewhere) to send reports to specified users at specified intervals. The specified intervals are listed here so that we may know when (at server time) is an email supposed to be sent.