PM Recurring Pattern Uses RRule*
Path: PMs Tabs
We have revised the Calendar Schedule section for PMs on the PMs Tab for both Tasks and Items.
For many years, our clients have requested a way to schedule for the third Tuesday, a given day of the week, or other specific pattern. You can do that with this new recurring pattern that is similar to MS Outlook or iCal.
The change allows you to be more precise in setting dates as well as selecting multiple days of the week for a single schedule. Previously, two different schedules were needed to specify different days.
The change employs an industry standard (RRule) in calendaring that implements the same standard recurring events you can see in email applications such as Outlook, Gmail, etc.
RRule is an industry standard in calendaring that implements the same standard recurring events you can see in email applications such as Outlook, Gmail, etc. This gives you more exact generation of PMs either by a date or a recurrence pattern.
The difference you see on the WebTMA interface is a few more options on the window. This update also provides projected dates.
When changing the schedule, you can see the next four projected dates to give you a sense of how this works. Be sure to test these settings to gain a better understanding of the process because it is somewhat different from the previous settings.
Following are examples of results when using a setting by Day or Day of Week:
Setting for Day 14 Would give the following dates:
Friday, Mar 14, 2025
Monday, Apr 14, 2025
Wednesday, May 14, 2025
Saturday, Jun 14, 2025
Setting for the Second Friday has the following results:
Friday, Mar 14, 2025
Friday, Apr 11, 2025
Friday, May 9, 2025
Friday, Jun 13, 2025
NOTE: Floating Schedules are NOT supported by the RRule. Currently, existing PMs use the old style, and new PMs follow the RRule. For new dual-based (Meter and Calendar) PMs, the calendar portion follows the new rules. In a future release, you will be able to change existing PMs to the new rule.
This was a February Voice of the Customer enhancement that was slightly delayed because of the complexity of the enhancement. We would like to thank Cencora for submitting this suggestion. We saw an opportunity to redevelop the page to be more user-friendly in all areas. WebTMA has evolved into the solution it is largely through great feedback and suggestions provided by our clients.
* RRule refers to a rule or repeating pattern for recurring events.
Batch PM Update Supports New Recurrence Rules
Path: Admin > Batch PM Update
The new PM Recurring Pattern that uses the industry standard RRule has been extended to the Batch PM Update window.
As a reminder, the new calendar scheduling rules apply to Fixed PMs. The previous rules apply to Floating PMs.
All desired check boxes must be marked to save changes.
If you have not completed all required fields for the new scheduling rules, an alert notifies you that, “Next PM Date, Interval, and Frequency are required.”
QP Cost Account # Now Defaults to WO Costs
Path: Transactions > Quick Post > Quick Post Cost
Path: Transactions > Work Order > Records / Cost Tab
Costs entered from the Quick Post windows frequently have an associated Account # that automatically populates that field. Previously, that Account # did not carry over to the related cost line on the Work Order / Cost Tab. With this change, the account number displays on the Work Order cost line regardless of limits placed on the Account # field (described in the Details below).
Your System Administrator can disable the Account # field from Admin > Form Attributes > System Form Attributes so the account cannot be changed on the Quick Post window. Regardless of this setting, the Account # still appears on the Work Order cost line.
For example: The Account # field on the Quick Post Time Labor Entry window is disabled. The intention is to prevent a user from manually changing the Account #. At the same time, the client wants the default Account # to be saved to the database, i.e., to show up on the Work Order / Cost Tab. Note: The Account # populates the field with the number that is associated with the Technician record.
Additional Languages Supported in WebTMA 7
WebTMA now supports the languages listed below for default text labels, menus, and messages. Words entered by your users in text fields are not translated (Comment field, Name field, Request, etc.).
Except for Malay, these languages are also accessible from legacy mobile products as well.
Your WebTMA Administrator determines the default language used in the application; however, individual users’ preferred settings can be made from the User record or from the File > Personal Info window. These settings override the Client Info selection.
NOTE: If you change the personal or User record settings, log out of the system. When you log in again, you can see the language change.
The following list shows the additional languages that are now supported:
- Greek
- Italian
- Japanese
- Korean
- Chinese Trad
- Arabic
- Russian
- Malay
- Turkish
Executive Dashboard Reject Request Option
Path: My Dashboard
Those who use the Executive Dashboard module on My Dashboard now have the option to Reject requests.
Previously, managers only had an Accept option for requests on the dashboard.
The new Reject column contains a red X button (reject) next to the green check button (Accept).
This is a March Voice of the Customer enhancement. We would like to thank Jefferson Health for submitting this suggestion. We saw an opportunity to redevelop the page to be more user-friendly in all areas. WebTMA has evolved into the solution it is largely through great feedback and suggestions provided by our clients.
Source Field Added to Work Order
Path: Transactions > Work Order > Records
A new System Source field has been added to the Work Order window.
Work Orders created by copying a Work Order now display "WO Copy" as the source in this new field and requestor details (name, phone, and email) are cleared on the copied work order
The first source available in this field is WO Copy; however, the source of some generated work orders, such as Failure Code, will be added in the future.
Look to the More Information section for the read-only System Source field.
The Work Order Source ID can be queried, found in reports, and is accessible in DDBC.
NOTE: When a new Work Order is created, this field remains blank by default.
Source Field Added to Notification & Escalation
Path: Admin > Notification & Escalation
The new Work Order Source concept is also applied in the Notification & Escalation window.
In the General Information section, look for the Source field. This is another optional rule for filtering work orders.
Currently, the Source field drop-down is available for IoT records and Work Order Copy. Failure Code will be available in the future.
Like the Work Order System Source field, the Work Order Source ID can be queried, found in reports, and is accessible in DDBC for Notification & Escalation.
'Require Failure Code to Close' on Task Window
Path: Organization > Task > Records / Identity Tab
The Tasks / Identity Tab now has a Require Failure Code to Close check box.
This feature makes sure that the Failure Code is always indicated.
By marking the new check box, you can assure that Work Orders that require Failure Codes always have them before the Work Order can be closed.
This applies to in-application records and is not currently available in mobile devices; however, it will be enhanced at a later date.
New Work Order Field: Last Sensor Notification
Path: Transactions > Work Order > Records / Identity Tab – More Information
Work Orders generated through the Smart Business Integration module show this field to indicate the last time an alert was sent from the sensor regarding a failure issue.
Since the outside software continues to send frequent alerts after the Work Order has been created, the date and time in this field assures you that the alert has been received and is still an active problem.
The field is only visible if the read-only Source System is one of the IoT sources.
Make Queries Public, Public/No Edit, or Private
Example of Owner Indicator for Public/No Edit
When you use the Find flyout, you can create either a one-time search or save your query for repeated use and select designated access.
When you click the Save Query or Save Query As button, the Query Access flyout gives you several options.
You can designate the Repair Center to which the query applies or leave it blank and search all Repair Centers.
In addition, you can designate who can see or use the query.
Here are the properties of the three settings:
- Public. This query is available to all users. Anyone can save or delete the query.
- Public/No Edit. Users can view and use the query, but they cannot save or delete the query. Only the owner, i.e., the person who created it, can make changes.
- Private. The query is invisible to all users except the owner. Only the owner can save or delete this query.
New UI Context Sensitive Help
Context sensitive help is now available for the new UI windows.
Click the Question Mark icon at the upper right to open online help about the current page.
The new windows now open Help the same as using the Question Mark icon in other parts of WebTMA 7.
Material Request Added to Service Request Portal
Path: Admin > Form Attributes > Service Request Portal–Material Request
The Service Request Portal (SRP) now includes a Material Request form that allows your requestors to ask for the Parts or materials they need.
This is another enhancement to SRP to make your request links easy to create and easy for requestors to use.
Like other SRP forms, you can use the Block Palette to drag the desired features to your Material Request page.
Standard buttons, links, Requestor, and Organization blocks are available.
In addition, Parts, Sales, and shipping information can be added.
Map Action Requested and Comments in Service Request Portal (SRP)
Path: Admin > Form Attributes > Service Request Portal
Contents of the Custom Text Field block (found in the Custom Affixed section of the Service Request Form) can be mapped to certain other fields. This allows you to append the contents to the mapped field.
When you edit your Custom Text Field, you can specify whether to affix the field values to the Action Requested or Additional Comments fields in your Form.
Field values are concatenated in the Action Requested or Comments fields.
Frequently, this is information that does not show on the Work Order but is needed by a Technician.
Service Request Portal Allows Dept.–Acct. Auto-Population
Path: Admin > Forms > Service Request Portal
The Service Request Submission and Material Request Submission Forms have default auto-populating behaviors for Department and Account blocks.
If the Form includes both the Department and Account blocks, an entry in the Department field causes the Account field to be populated with the Department’s Account number.
If the logged-in user accessing a Form has an assigned Department, the Department field is automatically populated with the user’s Department.
UPI - AP Payment Import Column Added
Path: Admin > Universal Interface
If you use the Universal Procurement Interface to import AP Payments into WebTMA 7, you can specify line-item payments in the Mappings Grid.
The columns include:
• Payment Amount (from line-item)
• Amount (from header)
Both are listed by default in the Mappings Grid.
Column Added to UPI - AP Invoice Export
Path: Admin > Universal Interface
If you use the Universal Procurement Interface to export AP Invoices from WebTMA 7, you have a new Column selection.
An Extended Cost column has been added to the WebTMA Column selection drop-down list.
Use this field to map to your Remote Column.
UPI - AP Invoice Export Now Includes UDF Values
Path: Admin > Universal Interface Setup / UPI – AP Invoice Export (Transaction Type)
The UPI – AP Invoice Export Transaction Type for the Universal Interface module, now includes UDF fields for column selection. Previously, the UDF fields were not available.
UPI - PO Export Has Double Quote Option
Path: Admin > Universal Interface Setup / UPI – Purchase Order Export (Transaction Type)
When some clients export to another application, their lines may contain commas, tabs, and special characters. This causes errors when importing to the outside application.
You now have the option to export the flat file and use double quotes if you have updated services. Since this is not needed by most users, updated services are required to use the enhancement.
UPI – Purchase Order Export – Re-export
Path: Material > Purchase > Purchase Orders
The Purchase Orders window has a feature related to UPI-Purchase Order Export. If the export fails, you now have a way to re-export the files.
This feature is also available for UPI-Purchase Requisition Export.
A Re-Export link on the Purchase Orders window Action Menu is available when needed.
The Re-Export link on the Purchase Requisitions window Action menu has the same purpose.
API Platform - PO and PR Linked Document Endpoints
Linked Document API endpoints are now available to export documents to your accounting system.
These are read-only documents that are attached to Purchase Orders and Purchase Requisitions.
You can transfer a read-only Linked Document that is attached to a Purchase Order or Purchase Requisition using the Swagger API Platform.
These new APIs are fully described in our Swagger documentation.
Inactivate Part Lines from Warehouse Module
Path: Material > Warehouses / Part Inventory Tab
The Warehouse / Part Inventory Tab includes an Active column with check boxes to inactivate a SKU line that has zero (0) Parts on-hand.
Previously, a change to the check boxes on the Warehouse / Part Inventory Tab did not save.
Having the option to inactivate SKU lines for several line items at one time is more efficient than opening each Part record to perform the same function on the Parts / Locations Tab.
If you save inactivated SKU lines on either the Warehouse window or the Parts window, the action is reflected on the appropriate Tabs of both windows.
NOTE: This does not inactivate the entire Part record. It only affects lines on the Part Inventory or Locations Tabs with zero (0) Parts on-hand.
Delete Sales Order Pending Items
Path: Material > Sales > Sales Order
Sales Orders are used to sell (charge) materials to various departments within your organization. If your order exceeds the amount on hand, items are back-ordered.
Pending Items on the Action Menu is used to see if back-ordered items are in stock. Line items only display when stock is available.
The Pending Items flyout now includes an option to delete items you do not need.
When you select a Department in the upper grid, the back-ordered items now available are visible in the lower grid.
Check the lines you want to delete and click the Delete link to remove them.
Mass Import Templates for Meters
Path: Admin > Mass Import
Our customers continue to request enhancements to the Mass Import module, and in response, WebTMA continues to add more templates.
With this release, you have two new selections:
- Meter
- Meter Type
Like other Templates for Mass Import, you can download and complete the spreadsheet before creating an import.
Mass Import Template for Meter Readings
Path: Admin > Mass Import
Our customers continue to request enhancements to the Mass Import module, and in response, WebTMA continues to add more templates.
With this release, you can now import Meter Readings.
Like other Templates for Mass Import, you can download and complete the spreadsheet before creating an import.
Email Multiple Techs from WO Schedule Tab
Path: Transactions > Work Order > Records / Schedule Tab
The Work Order / Schedule Tab includes icons to Email details to a Technician.
When more than one Technician is assigned to the work, you can now click the icon in the heading to open a flyout window and select some or all Technicians who need to have the message.
This feature was available for those who used WebTMA v5, and it is now included in WebTMA v7 as well.
Trade Window Shows Inactive Technicians
Path: Organization > Repair Center > Trade / Technician Tab
The Trade / Technician Tab has a new Active column. Empty check boxes indicate an Inactive Technician. The check boxes are read-only.
Previously, the list on the Trade / Technician Tab did not distinguish between Active or Inactive Technicians.
When a Technician record is marked Inactive, this is now reflected on the Trade / Technician Tab.
UDF Field Name Visibility Extended for Request Log
Path: Transactions > Request > Request Log
If your UDF options have very long names, you can now see the full name by hovering over the ellipsis in the drop-down list.
Previously, the selection only showed the first 50 characters although the field can allow up to 250 characters.
With this change, hover your cursor over the field and ellipsis to see the full name in the tool-tip. The illustrations above show the view “before” and the new “after” view.
Analytics Grid Layout
Path: Reports > Analytics
For clients who purchase the Business Intelligence feature, the additional Analytics module presents a list of your reports in an easy to search grid format.
Use the Filter icon to search for Analytics and see your results.
medTester Interface for WebTMA 7
Path: Admin > medTester Exception
We have updated the medTester Interface to work with WebTMA version 7. Many WebTMA healthcare clients heavily use the medTester product for electrical safety testing and performance verification.
The WebTMA 7 medTester Interface performs the same functions as in version 5 with a few changes for ease of use.
NOTE: You will need to configure a TMA user account with credentials in TMA to use the medTester functionality even if you use SSO to log into the main application.
Button Functionality
A Login to WebTMA button has been added as a main button. This is more convenient than having it on the menu.
The Generate Checklist / Upload to medTester button performs the same functions as two separate buttons in the previous version (“Send All Checklists” and “Send Filtered Checklist”). You have the option to filter for certain files or simply click Send without filtering before uploading files. Using this button pulls checklist data from WebTMA; creates import files; and pushes the files to the medTester Device.
A new Resend Check List to medTester button is used to resubmit, when needed, the files that were uploaded using the Generate Checklist / Upload button described above.
To provide better understanding of the functions it performs, the Download from medTester / Submit Results button is a new name for “Resend Last medTester Files”. It downloads check results from the medTester Device, writes them as a file, reads the file, and submits to WebTMA.
Another new button name is Re-Submit Results (formerly “Upload Results”). It was renamed to make it more consistent and better explain its use. Click the button to see a prompt for a result set that has been previously generated by medTester and re-submit it to WebTMA to resolve Sync Exceptions.
Changes
When results from medTester (MUP files) are submitted to WebTMA and the entire dataset is processed without any errors or exceptions, the file is automatically moved to a Processed subfolder.
If the dataset generates errors or exceptions, the file remains where it is and a medTester Exception record is generated that can be seen in WebTMA (Admin > medTester Exception). Exception records cannot be added, edited, or deleted.
Exception records are resolved by re-submitting the results after correcting any issues. For example, missing Biomed Equipment (usually missing related to data access) or invalid data in WebTMA (wrong Tech ID, invalid task, etc.). To correct the data before resubmitting, update in either medTester or WebTMA records, depending on the source.
Once you resubmit data and it processes successfully, the medTester Exception record is updated as ‘Resolved’ and the Is Valid flag is cleared.