Toggle Sidebar
  • Recent updates
    • Post is under moderation
      Oftentimes, customers ask for the ability to create multiple subtasks based off of template items (most times stored in an Aux table). This requires an Orchestration to be written today. I propose hav...ing a transition and/or transition action that can be used to create multiple items based off a report definition. Today, to create multiple items, the customer needs to utilize the Orchestration component of the tool. I'd like to see this become a Transition type, similar to the existing Post transitions. However, as you are defining the post transition, add a "Report Definition" section to allow you the ability to define the template items that you are going to recreate. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      With SBM 10.1.5 came the ability to share dashboards to groups (and even pin them to a particular group http://www.serenacentral.com/blogs/entry/share-and-autopin-dashboards-or-other-views ). I would ...like you to take this feature one further to be able to pin an individual report on a system dashboard of a certain group. Most of our users do not need a plethora of dashboards, so being able to customize the system dashboards for them would be the best approach. Less clutter, more function. Currently in oder to achieve this we need to either edit every users dashboards one by one or give the users instructions how to do it themselves. Both of these options are not very compelling. For a standard user we currently have the choice between two options: 1. leave default dashboards empty, then pin some dashboards specific to his group - his default view is empty, you need to explain to him how to go to which dashboard to do what he needs to. - wasted space on his default view 2. fill the system dashboards with a bunch of "default reports". - really useful for few users - since all users will visualize these default views, without really needing them the system load will be much higher then needed on the DB and the server - most users will still need to add custom dashboards or we need to push group specific dashboards - a new user will be overwhelmed by the clutter. It would be much better to leave the system dashboards empty (save for maybe the ONE report everyone finds useful), then push group specific reports on the system dashboards. Another option would be to be able to hide all system dashboards, like it is already possible with the "HOME" view via web administrator, then share only group specific dashboards. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Mike Dameron
      Allow Spanning for Dashboard Widgets I have a few users that are beta'ing our Work Center interface in preparation for migrating over completely to Work Center.  One complaint I'm getting is the inabi...lity to make a widget span an entire row in their dashboards.  They're looking for functionality similar to the layouts of a multi-view report where they can put a widget on top to span the full row, while widgets underneath only go to the specific colum.  More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Mike Dameron
      Some minor improvements to AppScripts would be helpful: Ability to read/write BLOB field types Ability to run AppScripts on Aux table adds and edits immediately A few more high-level function cal...ls that access code already written within SBM (e.g. Base64 encoding/decoding, etc) Access to TS_GUID More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Currently, subrelational fields are available when creating notification rules, but they aren't available when specifying the Delay Parameters on Escalations.
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Currently, subrelational fields are available when creating notification rules, but they aren't available when specifying the Delay Parameters on Escalations.
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Mike Dameron
      Allow highlighting of text in text fields Allow highlighting of text in text fields
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      SBM should offer a scheduler to start and execute processes or batches of processes. A process is defined as any of the following:    appScript    Orchestration    import definition set in SBM System ...admin import tool     Other misc data process SBM should support a scheduler to start and execute processes or batches of processes. A process is defined as any of the following:    appScript    Orchestration    import definition set in SBM System admin import tool     Other misc data process    A batch and a process should support the following parameters    Start time    reoccurring execution interval     length of time that audit history should be maintained    name    type (script, orch, import definition set, CopyValueFromFieldToAnotherField, CopyThisValueToThisField, DeleteRecords, ExecuteCommand)    Execution order - for processes that are included in a batch    Log Level (error, info, debug)    ActiveInactive    The parameters for each type will vary. For example,     CopyValueFromFieldToAnotherField : Name, Table, where clause, Source Field, Destination Field         CopyThisValueToThisField  : Name, Table, where clause, Value, Destination Field             DeleteRecords  : Name, Table, where clause     ExecuteCommand  : Name, Command Line, Command line parameter     The activities that the scheduler performs should be audited with the following details:    start time    time completed    total execution time    Result Summary of execution     Currently Running    The definition of scheduled processes should be creatable via the web interface. Individual processes should also offer the ability to allow the user to run the process immediately. Process and batches should be allowed to be set to inactive so they are not executed by the scheduler yet they remain in place so that they can be enabled at a later date. All Processes and batches should be promotable via the application repository manager. I have produced this type of system for multiple clients over the past 10 years. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      When handling more complex screens in SBM it would be very useful that we should not have save all data into the SBM item before it can be used in the orchestration. But that it should be possible to ...directly pass this data to the orchestration. When handling more complex screens in SBM it would be very useful that we should not have save all data into the SBM item before it can be used in the orchestration. But that it should be possible to directly pass this data to the orchestration. This would limit the amount of duplicate data and would make it possible to create more powerful applications with SBM. This data could then directly integrate with other SBM application and other external systems with having to switch between systems. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Mike Dameron
      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.

  • DateTitle
    10/01/2018 Allow subrelational fields in escalation delay parameters