Toggle Sidebar
  • Recent updates
    • Post is under moderation
      Nami Saiga
      There are lots of ways currently to filter the values shows in a relational field. Typically these require a dependency and another relational field by essentially creating a cross join between values... between two auxiliary tables related to the same primary table as well as each other. This works fine when you have the three table triangle setup or when you don't mind all values begin filtered the same for an entire workflow. However, it would be nice to see the potential for filtering these relational records extended beyond dependencies. For example, between related primary tables. We have a Change Management application that has a relational field pointed at the CI records in our CMDB application. In many instances, we would like to be able to filter the list of CIs available in the relational field depending on the CI type, the state it might be in; the list of possible filters is endless. In theory, I'd like to see (in Composer) the filtering properties of a relational field have a similar interface as that of an embedded report. I'd like to create a listing report against my primary or auxiliary table, get the reference link for that report, and then have that populate the list of items returned in my relational field. The upside to this would be... 1: I can control the values returned in any way I want without having to manage a dependency or have additional aux tables. 2: The filtering would not be dependent on the workflow. 3: I could control the presentation of the results, rather than relying on the value display format (which for us changes depending on the context we are viewing the item in . More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Nami Saiga
      Currently once the localization value has been created, it is not possible to delete them.Created values continues to remain although user remove any locale from Predefined Locales list.It means that ...unexpected string will be used ever since. Expected behavior: A: If user delete a locale from Predefined Locales, user can select the option which delete the all related localization values too automatically or not. B: User can clean up localization value manually in Application Administrator. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Nami Saiga
      Nami Saiga unlocked the badge Newbie
      Newbie
      Congrats on registering on the site!
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Nami Saiga
      Nami Saiga just registered on the site
      Stream item published successfully. Item will now be visible on your stream.
  • No blogs available.

  • DateTitle
    03/03/2017 Delete the localization value by user