Posted: 31 Jul 2017 9:28 EDT Last activity: 11 Aug 2017 8:46 EDT
Ask the Expert - Localization & Accessibility with Shahi Naquash & Srinivas Kakani
Join Shahi Naquash & Srinivas Kakaniin this month's Ask the Expert session on Localization and Accessibility!
Meet Shahi: Shahi is an Associate Product Owner for Pega UI and has been with Pega for 5 years. He has hands-on experience on building Demos and Implementations. He has been handling the controls area of UI for the last 3 years. Along with UI, Shahi also works on localization of the Pega platform.
Message from Shahi: Hello, I would like to answer your question related to localization, especially about any issues related to it and I would be happy to help you get a better understanding of it.
Meet Srinivas:Srinivas is a Product Owner for Pega UI. He has been with Pega for about 4 years now and worked in Platform Engineering (UI Engine) and then moved on to Product Management. He owns the Accessibility features of the product. Other feature areas that he primarily drives and collaborates-on include repeating structures (Grids and RDL), PDF Export, infrastructure components of UI Engine and Web-Mashup. He brings the unique combination of engineering excellence and product vision to the Pega platform.
Message from Srinivas: Hello, it’s always interesting and humbling to hear from and help the Pega community. Please reach out to me with your UI related questions, specifically on Accessibility, or UI in general and I will be happy to answer.
We had a similiar use case on my current project, in that case the 'Page' was a data page; in this instance we used a declare expression to propogate a property on the same page as the FV in order to surface the value (a count).
Hi Binod- Validations in screen flows have two different patterns based on how we navigate back and forth. Validations are fired when using the breadcrumbs / tabs, but not when the back button. This behavior is available from ML8.
Is there any specific behavior that you are looking for?
We are looking for a behaviour which does not do any validations(both server and client ) on click of breadcrumbs/tabs. I have read a post from you on mesh which says it is possible and is fixed in later versions. Can you please help. I have observed that behaviour of both the scenarios(click of breadcrumbs and click of back button ) is the same and it is firing client side validations / edit validate on the properties .
hi Binod- The default behavior is what I described earlier. We did try to overload a configuration check box on the assignment shape (an unchecked Perform post-processing when navigating away from step) to mean ignoring validations when going back and forth. This was mainly done with offline scenarios as the target usecases. However, this was reverted out at the late stages. I assume you are referring to this change related mesh document.
The screenflow harness is available rule, and the buttons are customizable. The behavior of not triggering validations when using the back button can be configured. The button has a runscript action to call pega.u.d.submit By passing "pyActivity=GoToPreviousTask&previousAssignment=true" as a parameter to this call, the client validations can be turned off.
Also, I think, you can try to force validations to be ignored by setting pyFlowData.pyDeferErrors (again, I think, from "pyGetFlowDataDefaults" activity).
And finally I want to add that we have some ideas in the backlog to streamline these behaviors further (as yet unprioritized and still at an idea stage).
Looked at your question. As a feature, I think we do support the scenario that you described. This needs some digging before we can get back on that. Either Shahi or I will be respond back on the original thread.
Hello. I faced an issue while was utilizing the Localization Wizard. I downloaded a zip-file, unpacked, provided changes to TextToTranslate.xml, packed a zip and uploaded the new file to Pega application.
Is there any restriction present for accessing Pega from MAC book? Our application is built in Pega 7.1.8 and we have IAC configured to access application externally. Our application is running in cloud. When the user tried to access our application using Chrome browser in her MAC book below exception occurred[User accessed IAC link].
Exception: PRGATEWAY EXCEPTION @ error- response form PRPC.
There is no restrictions on accessing Pega content from a Mac machine. Chrome on Mac is supported. Note that starting with Pega 7.2.1, we support Pega WebMashup without needing a gateway.
Unfortunately, the provided information is not enough for me to make any educated guesses as to what is causing it. Please check your PRPC logs to see if there is more information. Make sure that your prgateway setting are fine. If still need more help, please create a different thread so more people could participate on the specific kind of issue.
we are using a repeating grid (used in both Editable and Read only). we are showing status as Image (Lock and unlock symbols) and we have written tooltips for these images. So when i do TAB from start of the screen, control will skip this and goes to next. is this Fine? Will there be any chance of failure when using any of the accessibility tools?
In general, Is using Images in grids is fine with respect to accessible users?
I think we can all agree that images are not accessible! So ideally it would be good to avoid them when conveying information that could be text.
I'm assuming you have a section include with visibility conditions on Lock/Unlock images. Out of box, we have a when rule "isAccessible" which tests for the access group setting for accessibility. You can configure your section to show either text or icon based on that when rule to drive the cell visibility conditions.
We do generate the title text configured as the alt text of the image as well. And in a repeat grid, we can always focus the first column in the grid using the tab key. And any other column that has an actionable element (button/link/image with actions configured on it) can be focused using tab key. To access data-only columns in any grid, the user needs to use table navigation mechanism of the screen reader instead of using the tab key.