Axxerion Integration with the Workday HR System
By Mehdi Khalvati
With Axxerion’s out-of-the-box and API integrations connecting your IWMS and CMMS to an HR system like Workday is both easy and effective. Axxerion implementation specialists specifically configure the Workday integration into the IWMS/CMMS according to each company’s needs. This eliminates the tedious manual processes of dual data entry into separate systems.
Further, it allows for streamlined tasks between facilities and HR departments, and decisions are made based on current and accurate shared information. While there are many different ways Axxerion can configure this HR integration for its users, here are some specific features of the IWMS/CMMS integration with Workday:
- Workday File Imports
- Employee Onboarding and Offboarding
- Roles and System Access
- Single Sign-On (SSO)
- Floor Plan View
- Employee Moves
- Tracking Occupancy
- Work Orders and Timesheets
- Collaboration and Space Planning
In addition to Workday, Axxerion’s powerful and flexible IWMS and CMMS solutions offer many different integrations… The system also offers seamless transitions from:
- IBM Maximo
- IBM TRIRIGA
- Trimble Manhattan
- And more!
[Admin: This post is related to the 08.17.20 post by Axxerion about IWMS+, and the 08.01.16 post about the CAFM, CMMS, EAM, and IWMS competitors of IBM TRIRIGA. To see other related posts, use the Axxerion tag.]
So far I’ve been using triplat-query-filter… This works fine, but I want to search for multiple different names at once. Now I could use a triplat-query-or tag and just use another filter for firstName, but I want the amount of these to be variable, so this wouldn’t be a practical solution. Is there a simple way for me to do this?
Your problem is that there is no “in” operator available. I would suggest you to take a look on the triplat-ds-core, because it allows you to programmatically create the query filters… The triplat-ds-core substitutes the triplat-ds and offers a low-level API. It should not be placed as a child of triplat-query or triplat-ds.
To run the triplat-ds-core you need to call the method “generateRequest”. That method will return a promise that resolves to a result object that contains the queried records. Remember to replace the workersModelAndViewName in the context property. You should use the exposed name of the modelAndView used by your application.
[Admin: To see other related posts, use the Query tag or Filter tag.]
We can’t export the graphic floor map to PDF from TRIRIGA. The system is “hanging” and not exporting. This is only happening with some drawings and only occurs when using Layer 0 from the Xref file ( xrefdwg | 0 ). If all other layers are off and a layer zero from any Xref is displayed on the graphics section, even if empty, the export will fail to complete.
The export graphic was throwing a malformed XML exception. The root cause was that there was a “1 = 1” element that got pulled in from the layout of an attached Xref onto layer 0 on that Xref. It turns out that, for any text element that contains any equals sign, the process of sending the SVG from the client to server using a Dojo API to post via a hidden input element, resulted in extra double quotes getting sent, and causing the SVG XML to be malformed.
We resolved this by pre-processing the SVG sent to the server to remove these extra double quotes, before sending it to the SVG converter. Moving forward, the export graphic will now successfully export a graphics section that includes text that contains any equals sign. Text that contains both double quotes and equals in it, will get the double quotes removed for technical reasons.
[Admin: To see other related posts, use the Xref tag or SVG tag.]
With the emergence of new workplace models and technologies, we are starting to see a shift away from traditional Integrated Workplace Management Systems (IWMS) to stand-alone software systems integrated through common APIs in order to achieve true best of breed capabilities across multiple service needs. In fact, one of the original founders of the IWMS concept, Michael Bell, has defined this shift as IWMS 2.0. According to Mr. Bell, IWMS 2.0 has the potential to achieve lower costs, faster implementation and valuable data-driven insights…
At Lighthouse.io, we are strongly aligned with Michael Bell’s IWMS 2.0 vision. We are focused on solving very specific challenges for facilities managers… For a facility manager, these challenges form only one part of their overall remit. Whilst it’s tempting to build out a system that covers the entire facilities management function, we realize that by doing so we would be sacrificing the quality of our core product. Therefore, our preference is to integrate with complimentary products that are best of breed and solve a different set of challenges for facilities managers.
To illustrate the IWMS 2.0 model in practice, let’s explore how Lighthouse.io could integrate with another best in breed software product – Serraview. Serraview is a leader in space planning and management. Lighthouse.io is a leader in commercial cleaning software and optimizing delivery of facilities services. Combined, these two products can provide facility managers with an end-to-end solution for managing employees, assets, and delivery of facilities services…
[Admin: This post is related to the 08.01.16 post about the competitors of IBM TRIRIGA. To see other related posts, use the Serraview tag.]
In the Admin Console, Performance Monitor, when monitoring a single value, it returns bad results. Returns wrong agent’s status. Returns “false” for an agent status even if the agent is running. Returns “0” for the number of agents running even if multiple agents are running.
We needed to update the calls to various platform status APIs. Moving forward, we updated the Admin Console, Performance Monitor, Single Value to correctly obtain the status of the active agents. This means the AGENTS_RUNNING_COUNT, OBJECT_PUBLISH_AGENT_RUNNING, SCHEDULER_AGENT_RUNNING, and all other agent-related monitors will now correctly report the agent status and count. We also removed the calls to KEYWORD_PARSER_AGENT_RUNNING and WAREHOUSE_AGENT_RUNNING as these no longer exist.
[Admin: This post is related to the 04.08.15 post about performance monitoring tools, and the 02.10.17 post about performance best practices.]
Is the integrated workplace management system (IWMS) right for the modern workplace? Today’s workplace has new requirements that have pushed the boundaries of what the workplace management tools and practices of yesterday can support. There’s a new IWMS model that can leverage existing investments and better support the workplace of the future…
Michael Bell, who is one of the original founders of the concept IWMS, issued a paper recently called IWMS 2.0 where he talks about the power of using multiple different stand-alone systems integrated through common APIs in order to achieve true best of breed capabilities across multiple service needs.
The benefits of these applications are that they can really truly focus on their core components. Applications such as Serraview being entirely space management focused mean that you have the ability to ensure that the capabilities and functionality are continually being developed and evolved…
After an upload of a document, we use a custom task to send the document to a FileNet instance for content searchability. From that point, we don’t need the document in the TRIRIGA database any longer.
Is there any simple way to delete the content associated to a document record? This ensures we have control over where documents and sensitive information are being stored, and to save database space. From reviewing the API, it looks like we might be able to achieve this in our custom task with .setContent(null or empty content). Is there a nicer approach?
[Admin: This post is related to the 12.02.16 post about integrating with a CMIS or ECM, and the 06.09.16 post about using an ECM instead of Document Manager.]
Component API documentation for developing applications with UX Framework is deployed with your TRIRIGA server. Component documentation can be accessed via the following endpoint:
- The [tririga-hostname:port] and [/context_path] are the specific values you’d normally use to access your IBM TRIRIGA environment.
Once at the component documentation page, you can browse or search the TRIRIGA delivered components that are available on your specific platform version using the left-hand panel. Further down in the list, you can find documentation for the available third-party components delivered with the corresponding version of Google Polymer. (This version varies, based on the TRIRIGA platform version. See the Compatibility Matrix for more information.)
In the right hand panel, the documentation provides information about the selected component, generally with sample usage, styling and an API reference. In some cases, there are also demos available. You can toggle between the Doc and the Demo for a component using the buttons in the top right of the page…
[Admin: Similar content is also found in UX Article 2: Implementing UX. This post is related to the 12.11.15 post about the UX framework.]
In IE11, when you open a task directly from the Gantt chart, the popup window opens behind the Project form.
With the TreeGrid API, we needed to suppress all next actions to resolve focus issues with IE. Moving forward, an issue has been fixed in IE where the Task popup window appears behind the Gantt Project form.
When learning about new technologies and tools, it often helps to get one’s hands just a little bit dirty and see what really makes them work. That’s the idea behind the new Bootcamp labs at IBM InterConnect 2017, March 19-23 in Las Vegas.
These instructor-led labs run 3 to 4 hours, giving enrollees the opportunity to do hands-on work with new products and technologies. Attendees can find a deeper dive in these sessions led by subject matter experts…
IoT Platform to Maximo/TRIRIGA hands-on lab
Thursday, 8:30 AM – 12:15 PM, Mandalay Bay South Seas I1, Session ID: 7436A
This lab offers attendees a basic understanding of how connected operations work. Use a simulated temperature sensor (a gauge meter in Maximo) to send a temperature reading to the Internet of Things (IoT) Quickstart. The message is then sent to NODE-RED, which parses the message. When a reading changes, it goes into a REST-API call that inserts the meter reading into the referenced asset meter readings. The reading updates the measure point and triggers a work order using Maximo functionality, or if one chooses to do so, using a TRIRIGA work task…
[Admin: This post is related to the 02.06.15 post about exploring the TRIRIGA user group community, and the 06.07.16 post about using sensors with Watson IoT to create TRIRIGA work tasks.]