91 Matching Annotations
  1. Last 7 days
  2. docs-staging.docs.admlabs.aws.swinfra.net docs-staging.docs.admlabs.aws.swinfra.net
    1. Sorting

      Sort descending by creation_time:

      /api/shared_spaces/<space_ID>/sessions?fields=creation_time,end_time,user&query="(creation_time>%272026-01-28T20:59:59.427Z%27;creation_time<%272026-02-26T20:59:59.427Z%27)"&order_by=-creation_time

      Sorting ascending by end_time:

      https://qa8.almoctane.com/api/shared_spaces/1001/sessions?fields=creation_time,end_time,user,user&query="(creation_time>%272026-01-28T20:59:59.427Z%27;creation_time<%272026-02-26T20:59:59.427Z%27)"&order_by=end_time

    2. session_identifier

      After this section, before the Terminate sessions, Export section needs to be added with the 2 examples: -export to excel into a specified file /api/shared_spaces/<space_ID>/sessions/exports/file.xlsx?fields=id,user,client_type,session_identifier,client_ip,access_type,creation_time,end_time,license_edition&query="(creation_time>'2026-01-28T20:59:59.427Z')"&timezone=UTC+03:00

      -export to CSV file: https://qa8.almoctane.com/api/shared_spaces/1001/sessions/csv_exports?fields=id,user,client_type,session_identifier,client_ip,access_type,creation_time,end_time,license_edition&query="(creation_time>'2026-01-28T20:59:59.427Z')"

    3. Grouping

      Example for grouping by license type: /api/shared_spaces/<space_ID>/sessions/groups?group_by=license_edition&query="(creation_time>%272026-01-28T20:59:59.427Z%27;creation_time<%272026-02-26T20:59:59.427Z%27)"

    4. Filtering

      example for filtering by the user ID: api/shared_spaces/<space_ID>/sessions?fields=session_identifier,client_type,user,creation_time,access_type,license_edition,end_time,client_ip,id&query="(creation_time>'2026-01-28T20:59:59.427Z';creation_time<'2025-11-27T20:59:59Z';(user={id=220001}))"

    5. ./api/shared_spaces/1001/sessions?fields=end_time,user,client_type&query="(end_time=null)"&order_by=start_time

      api/shared_spaces/<space_ID>/sessions?fields=creation_time,end_time,user,client_type&query="(creation_time GE ^2026-01-01T00:00:00Z^);(creation_time LE ^2026-01-30T23:59:59Z^)"

  3. Dec 2025
  4. docs-staging.docs.admlabs.aws.swinfra.net docs-staging.docs.admlabs.aws.swinfra.net
    1. Hidden fields can be included in emails sent by release process auto actions to disallowed users.

      If I remember correctly this is happening when hidden fields are passed as variables in add comment or send mail auto actions. I have tagged you in the comment I left on the correspondent US.

    2. Hidden field configuration is not applicable in Quality Criteria (QC) entities. Admin should not use fields that are hidden for other users, as the field label and value is displayed in the QC setting.

      This is a major gap in this functionality. Can we highlight it somehow? Not mandatory, but among the other limitations, this is the most dangerous one, as it affects the security of the hidden udf.

    3. Users with the Update Risk Settings permission can still override the original configuration, even if it contains hidden fields.

      Here we have a high defect. Let me know if the statement will make admin not grant edit permission on risk after reading this: When a user with the Update Risk Settings permission accesses the configuration, the original settings are automatically overridden.

    4. Users with the Shared Entities Management role can view and manage hidden fields in shared entities, regardless of other role restrictions.

      This statement is not correct.

      A user is required by the system to be assigned a workspace role in addition to the Shared Entities Management role.

      This is relevant to the hidden-field use case because of how field visibility is evaluated across roles:

      If a user has multiple roles and a UDF is hidden in some roles but visible in at least one role, the user will see the field.

      However, if a UDF is configured to be shown only for the Shared Entities Management role, the field will not be visible to any user.

      The reason is that Shared Entities Management alone is not sufficient to grant field visibility in the workspace context. To make the field visible, at least one workspace role must be selected in the “Show only” configuration.

      In short, field visibility must be granted through a workspace role; otherwise, the field remains hidden even if Shared Entities Management is selected.

    5. Hide field

      We need a link for details about Hide field ability, same as we have for Searchable or Treandable fields. It will be used in a tooltip in the application, so admin can directly access it. Same for the limitations section.

  5. docs-staging.docs.admlabs.aws.swinfra.net docs-staging.docs.admlabs.aws.swinfra.net
    1. Endpoint

      We need to note here that sessions must be filtered either by specific session IDs or by their creation date within a 30-day interval.

      ALM-OCTANE-TECH-PREVIEW header is mandatory

    2. Export

      These parameters are not directly linked to this feature. These are generic parameters, available for all exports. We should display the examples for the APIs for exports.

  6. Oct 2025
  7. docs-staging.docs.admlabs.aws.swinfra.net docs-staging.docs.admlabs.aws.swinfra.net
    1. Referencing properties References to field properties can follow either of these syntaxes: entity.<property> or entity['<property>'] Example: entity.story_points, entity['story_points']

      We need to drop this and change in the entire page the examples for the formula; instead of entity['field_label'] we need to replace it with entity.field_label

  8. Sep 2025
  9. docs-staging.docs.admlabs.aws.swinfra.net docs-staging.docs.admlabs.aws.swinfra.net
    1. ))

      Please add another line below this one:

      isEqual(date1, date 2) DateUtils.isEqual(entity['done_date'], entity['last_modified']) Verifies if the values of 2 date fields are equal. '==' and '!=' are not supported for date fields.

    2. entiy[‘date_udf1’].Value!=entiy[‘date_udf2’].Value; entiy[‘date_udf’].Value==(new Date())

      Please replace the example with: Date.current() <= DateUtils.addWeeksToDate(entity['creation_time'], 2)

    3. 3)

      Please add before this line: DateUtils.addSecondsToDate(date, seconds) DateUtils.addSecondsToDate(entity['creation_time'],55) Adds the seconds to the date field value. Example and Description for this line: DateUtils.addMinutesToDate(entity['creation_time'], 30) Adds the minutes to the date field value.

    4. )

      Example and Description: DateUtils.subtractMinutes(entity['last_modified'],55) Subtracts a specified number of minutes from a date field value.

      Please add a line for DateUtils.subtractYears(date, years)

    5. subtractWorkDays(date,days)

      Replace the line with: subtractMonths(date, months) DateUtils.subtractMonths(entity['last_modified'],2) Subtracts a specified number of months from a date field value.

    6. DateUtils.addMinutesToDate(new Date(),2)

      Example and Description: DateUtils.subtractDays(entity['last_modified'],3) Subtracts a specified number of days from a date field value.

    7. Substracts

      Please add before this line: DateUtils.subtractSeconds(date, seconds) DateUtils.subtractSeconds(entity['last_modified'],55) Subtracts a specified number of seconds from a date field value.

    8. (entity[‘udf’] > entity[‘udf’].originalValue) ? entity[‘udf’] : entity[‘udf’].originalValue)

      originalValue is not implemented for Verve release. Let' replace with this one: (entity['story_points'] > entity['actual_story_points']) ? entity['story_points'] : entity['actual_story_points']

    9. count(enity.children

      CollectionUtils.count(entity.product_areas)

      we dont support yet children. But we support other fields that are Collections: application modules, multi value lists, teams, etc

    10. sum(collection) sum(entity.children.int_udf) Returns the sum of all entity's children's int value. avg(epression) avg(enity.children.story_points) Returns the average value calculated from all the entity’s children. count() count(enity.children)

      to be removed - all 3. Not implemented

    11. entity[‘story_points’],entity[‘actual_story_points’],entity[‘udf’],..

      Currently, we support also these annotations for calling the properties of the entities: entity.story_points; entity.actual_story_points. We should document both