Toggle Sidebar
  • Recent updates
    • Post is under moderation
      The SBM User fields currently use the SBM User accounts' "Name" field for search and display purposes in Single User and Multi-User Fields. In large organizations, it is common for multiple people to ...share the same name. In cases where the data comes into SBM via LDAP imports, there is no way to maintain a unique display name for each user unless it is stored in LDAP. Ideally, there would be some way to have SBM control how it renders the user in the user field value lists (in at least forms and report contexts). Possible approaches could include a VDF (Value Display Format) type of mechanism that allows the mapping of different LDAP attributes (aka User, Contact and Resource attributes) into the value displayed for the user fields. Additional options for forms could include a hover over action that shows additional attributes (such as simple hover text or a contact card) which may be too large to show within the value list directly. In our use case, we would like to have at least the business unit displayed in addition to the users name to help make the value distinct. Ideally, the exposed values would also factor into the search results. Or better yet, allow the search to search against the other User, Contact, and Resource fields). More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Allow editable grid to be configurable so that it can be ready for data input on a submit transition. Allow editable grid to be configurable so that it can be ready for data input on a submit transiti...on. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Currently, the Editable Grid template for listing reports does not have the Action menu option "Requery QAR Parameters" when the report contains Query at Runtime parameters. To be able to work around ...this limitation, a user must close and reopen the report OR first use Back to Listing, then Requery QAR Parameters (which assumes the template saved with the report). If the report was saved with the listing report template and not the editable grid template, an additional step is required to get back to the editable grid view again. To address this, it would be preferred that "Requery QAR Parameters" was added directly to the Editable Grid Action menu when the report contains Query at Runtime parameters. It would be preferred that when implemented, that the value shown is derived from the strings tables as is currently done in the listing report menu so that the actual string displayed can be customized if needed. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      SBM allows users with the "Logon as Another User" privilege the ability to choose ANY user. In some cases, this might be an otherwise lesser privileged user who could then impersonate an administrator.... As such, this feature often is only used by administrators due to concern for an abuse of this feature. It would be ideal if there was a way to control which users a given user could impersonate. For example, a test lead might impersonate a list of test users. Or a Manager might impersonate a direct report (to set up out of office settings, delegate settings, etc). Ideally it would allow an Administrator to specify who can be impersonated. But there might be use cases where an individual could specify someone who could act on their behalf as well (like delegate, but allow for changing user settings too). More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Relational fields can be created against Aux or Primary Tables. However, when using them for Primary tables, projects are often a factor. For example, if a user doesn't have permission to see items in... the project, they probably shouldn't be able to see them when selecting values for a relational field against that table. Additionally, even if they have permissions, maybe the SBM Developer only wants the list of values to come from a particular project. I could see part of this being addressed by an option in the SBM Web Admin as a field override. The permission thing is a slighly different matter as I believe it is enforced on the advanced lookup form, but not the quick search directly on the field control. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Allow the first value in a multirelational or multiselect field to drive sorting on a report if a report is set to allow sortable columns.  Currently, multirelational or multiselect fields do not sort... reports. Multirelational or multiselect fields can contain 1 or more values so using a multivalue field to determine sorting can be ambiguous if there is more than 1 value in the field. To rectify the ambiguous case, use the first value if there are more than 1 value in the field. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      This sort functionality should be available for all reports.
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Please add dynamically sortable columns to the drill-down reports that descend from a distribution report.  While you are at it, dynamically sortable columns would be nice in the in-built system repor...ts too.   Please add dynamically sortable columns to the drill-down reports that descend from a distribution report.  It's inconvenient to go in and edit the report's drill-down just to see a different sort.   With the system reports, no defined sort is even possible.   Particularly in the Users report, to be able to wade through the deleted users, I always have to copy and paste, because there is no export action, to Excel and sort and filter the data there.  These are all small things that detract from a great/expected experience.  More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      As an application designer, I would like a way to document environment or project specific changes that the system administrator needs to make before, during or after deploying a new or updated proces...s application. Add a Process-App level feature to Composer with a list of project-level changes that need to be made to fully support my new or changed process application.  For example, I added new fields to support new requirements for notifications and reports.  I would like to document what needs to be changed in the notifications and reports for the person doing the promotion to Production. The same applies to project-level over-rides, new Roles to be assigned to Groups or Users, Advanced Reporting views to be created, etc.   More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Muhammad Amad Sheikh
      Add support for shared mailboxes for notification server and mail services. I am quoting Microsoft technet page about shared mailboxes to be completely clear what type of mailbox we are talking about...."A shared mailbox is a type of user mailbox that doesn’t have its own user name and password. As a result, users can’t log into it them directly. To access a shared mailbox, users must first be granted Send As or Full Access permissions to the mailbox. Once that’s done, users sign into their own mailboxes and then access the shared mailbox by adding it to their Outlook profile. In Exchange 2003 and earlier, shared mailboxes were just a regular mailbox to which an administrator could grant delegate access. Beginning in Exchange 2007, shared mailboxes became their own recipient type."https://technet.microsoft.com/cs-cz/library/jj150498(v=exchg.150).aspx Currently, there is no way of defining access to shared mailbox. If we setup mail services like this: Login name: href="mailto:user.mail@domain.com">user.mail@domain.comMailbox e-mail address: href="mailto:shared.mailbox@domain.com">shared.mailbox@domain.comMailbox password: *****Password verification: ***** SBM is processing mails from href="mailto:user.mail@domain.com">user.mail@domain.com instead of href="mailto:shared.mailbox@domain.com.">shared.mailbox@domain.com. If we try to provide full path to mailbox like this: href="mailto:user.mail@domain.comshared.mailbox">user.mail@domain.comshared.mailbox Unfortunatelly, this and other similar forms of definition is not supported by SBM and results in configuration error. Some customers have already been interested in this option as they are planning on migrating to cloud and this type of mailboxes is a standard for technical accounts. More
      Stream item published successfully. Item will now be visible on your stream.
  • No blogs available.

  • DateTitle
    22/07/2016 Support for LDAP Groups and Synchronization