Toggle Sidebar
  • Recent updates
    • Post is under moderation
      When SBM is set to store file attachments in the database, the attachments go into the AE db. This can take up a lot of space and can pose security problems when the attachments contain sensitive info...rmation. I'l acknowledge that SBM is not a document content management system. I've worked with clients who expect it to be one and to offer the features of a real CMS. To that end, better handling of many large file attachments would allow placing those documents on a system which is more suitable for handling large records securely. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Sandeep Reddy K
      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.
  • No blogs available.

  • No entries were found