When the navigation item is saved with special characters, the user is unable to open the form. Upon clicking the item, an error is reported: “Due to either a session timeout or unauthorized access, you do not have permission to access this page.”
When you create a custom navigational link, if special characters are used such as /, \, &, #, %, they break the capability to redirect the user to a form or to an external link. Refrain from adding a special character. They must be omitted so that the form can be rendered.
[Admin: This post is related to the 01.29.18 post about restricting special characters in a text field. To see other related posts, use the Character tag.]
I am able to login to IBM TRIRIGA home with the default user name “system” and password “admin”. I would like to add a new user so that others can work on this application. But I am not able to figure out how to add a new user. I tried with the menu options: Portfolio > People, and Portfolio > Portfolio Set Up. But I am not getting any “user details” form to create an account. Can you help me out?
You are close. You just have one more click to go! :-) Once you are logged in as the system user, navigate to Portfolio > People as you listed above and then choose what type of user you want to add: Consultant, Employee, or External User. When you are in one of the following screens, you can add a user:
- [Home] > Portfolio > People > Consultants
- [Home] > Portfolio > People > Employees
- [Home] > Portfolio > People > External User
[Admin: This post is related to the 02.06.17 post about the quickest way to create 1000 native users. To see other related posts, use the People tag.]
Our customer has seen an issue when installing TRIRIGA 3.5.3 (Linux, Server build number: 276955) on an existing database (on 3.4.2 / 10.4.2). Everything goes well until starting up the server. Generally, TRIRIGA will run a database upgrade on the first startup when a build number difference is detected.
In the OM log, we notice that TRIRIGA tried to import the upgrade OM package… The import process started with the triPlatformObjectLabelManager package, but it failed to import a navigation item, which is newly created for Object Label Manager. I haven’t found any log which can explain this failure. I’ve checked the NAV_ITEM table. This navigation item wasn’t there before the upgrade process. Then all of the other packages are stuck on a pending status. Nothing happens after “Creating package from Zip file”. This behavior causes a lot of SQL update failures.
Meanwhile, on our Dev environment (Windows, Server build number: 279835), the upgrade went very well. You can find the difference in the logs. The OM log was set on “Debug” level on both servers. Note that the build number is slightly different between these two enviroments. Have you seen this kind of issue? Where can I find more details about the navigation item import failure?
[Admin: This post is related to the 02.17.17 post and 05.19.16 post about inconsistent OM validation results. To see other related posts, use the Object Migration tag or Upgrade tag.]
A navigation item whose target is set to “External URL” and whose URL links directly to a folder no longer works. An error such as the following might occur: “An error occurred, please contact your system administrator: [MID-4077624314].”
The Java applet that uploaded documents based on the navigation item target in earlier TRIRIGA versions is deprecated due to security concerns. Most browsers no longer support Java applets. The applet upload function is replaced with an HTML5 upload function.
As a result of these changes, “External URL” navigation items in earlier TRIRIGA versions that successfully uploaded documents via portals to upload documents to a folder might no longer work. The Document Upload widget was redesigned to be used only in the context of either Document Manager or a record, not a portal. Use Document Manager directly to upload documents.
[Admin: This post is related to the 04.07.17 post about “External URL” navigation items that may no longer work, and the 07.10.15 post and 04.10.15 post about the document upload enhancement. To see other related posts, use the Document Manager tag.]
I’m currently using my UX application to frequently add and modify new users. I’m using an iron-list to display these users and search through them. However, once I add a new user and navigate back to the list, I need to use the pagination buttons or refresh the entire page before the new user shows up. It’s not a massive issue, but it would be nice for the list to refresh when I navigate back. Does anyone have any tips on how to solve this?
When you navigate back to the page you can call the “refresh” method of the triplat-ds component. Have you tried that?
[Admin: To see other related posts, use the UX tag or UX Framework tag.]
I’ve been following the video tutorials on the UX framework, and I think I understand how triplat-route works now. However, I’m unsure how to navigate back to the main page from one of my elements in the iron-pages tag. Do I need to have a universal menu across my whole app? I’d prefer not to do that, if possible.
If you defined, in the root page, a home route like this:
<triplat-route id=”homeRoute” name=”home” path=”/”></triplat-route>
Then, inside a child page you can do this:
<triplat-route id=”homeRoute” name=”home”></triplat-route>
[Admin: To see other related posts, use the UX tag or UX Framework tag.]
In this day and age, security is a very hot topic. As soon as one vulnerability is addressed and mitigated, another one is found. It is a vicious circle of identifying and addressing vulnerabilities that does not seem to let up. In our fix pack release notes, information regarding the mitigation of vulnerabilities that were addressed without an APAR is listed. And sometimes, a vulnerability is addressed as an APAR.
The reason I am mentioning security vulnerabilities is that sometimes, when they are resolved, there is an impact on existing functionality, which may not always be clear. Sometimes, the result of fixing vulnerabilities can “change” functionality. As an example, in the TRIRIGA 3.5.2 release, external URL navigation items will now open in a new window to avoid cross-origin scripting vulnerabilities…
As the product develops and security vulnerabilities are found and addressed, it could mean a change in how something works. Reading the release notes can be a source of information, but it may not always be clear why something changed. We all know change is hard, especially when we are so used to it working in a certain way. I don’t know about you, but if the change was made to address a security vulnerability, I can live with that and accept the change.
[Admin: This post is related to the 04.07.17 post about APAR IV94912 where “External URL” navigation items may no longer work. To see other related posts, use the Security tag or Vulnerability tag.]
I am trying to create a web page using the UX framework. The current version I am using is TRIRIGA 3.5.1. I have a button, and on-tap, I want to display a new page. I have the basic code in place. But for some reason, the button does not do anything.
Initially, I was using <app-route>, but then I thought of using <triplat-route>. I’m not sure what is going on. I have commented out the button code, since I am not sure how the function would be called on the route. Can you please advise on how this is achieved? I am attaching my code for your reference…
You can navigate to a specific route by calling the navigate() route. Take a look at the attached file…
[Admin: To see other related posts, use the Routing tag.]
After migrating to TRIRIGA 126.96.36.199, we are experiencing an intermittent issue where saving group overrides in the navigation collection crashes TRIRIGA, and users are no longer able to login. Has anyone else experienced this issue before?
Between the TRIRIGA 3.3.2 and 3.5.2 releases, applets were removed, the Document Manager upload widget was updated, and new security constraints were put in place. As a result of these changes, any “External URL” navigation items that worked in 3.3.2.x to upload documents may no longer work…
After the change from the applet upload to the HTML5 upload, the widget can no longer be used directly in a portal section without a record context.