|
Core Platform
PRB1415408
|
The reference qualifier on a dot-walked field is not working if it is created
as a choice field |
When using a dot-walked field in a reference qualifier, and the user adjusts the
dot-walked field live on the form, the reference qualifier will adjust. This works
correctly as a string field, but not a choice field. If users create it as a
string field first, then change it to a choice field, it works as expected.
The fix for PRB1415408 is a property-controlled opt-in fix. Adding the property
com.glide.script.clientrecord .use_ordered_keys = true will cause 'current' to be
loaded in the ascending field order when values are being changed within a form.
In a case where multiple fields point to the same reference with different
qualifiers, the most granular reference will be honored when the property is
true.
|
- Create a scoped app called choicetest1 in Studio.
- Exit Studio and select choicetest1 as the selected application.
- Navigate to the tables module.
- Created two tables: potato1 and potato2.
- Open a record in potato2.
- Right-click on the context menu and select Configure Form
Layout.
- Create a field as follows and save.
- Name: Test
- Database column name: Test
- Type: Choice
- From the form, right-click Test and select
Configure choices.
- Add a, b, and c and save.
- Open form view for potato1.
- Create two reference fields to potato2: Ref1 and Ref2.
- Save the form layout.
- Adjust the form layout again and add a dot-walked field called Ref1.Test.
- Right-click Ref2 to add the advanced reference qualifier
'javascript:"testLIKE"+current.ref1.test;'.
If you do not populate ref1 and adjust Test choice Ref2 works fine with
qualifier. If you populate ref1, then adjust the test field and use Ref2, the
qualifier does not work as expected.
|
|
Transaction and Session Management
PRB1396897
|
A REST request without a JSESSIONID, but with a valid glide_user_activity token
in the cookie, fails with a 401 HTTP code |
The fix for PRB1396897 is disabled by default. To receive the fix for this
problem, users need to set the boolean property com.glide.processors.
httpauthprocessor. activity_cookie_check to 'true'. |
- Install the Agent Chat plugin.
- Log in as admin or any other user with the awa_agent role, without the
'Remember me' option selected.
- Navigate to /workspace.
- Open the Chrome developer window, and delete the JSESSIONID from the
cookie.
- On workspace, click the list icon to trigger a GraphQL request.
Expected behavior: The GraphqQL request should succeed.
Actual behavior: The GraphqQL request returns with a 401.
|
