Toggle Sidebar
  • Recent updates
    • Post is under moderation
      Agree. We use CyberArk to control access, but inside SDA are still forced to hardcode usernames and passwords in component steps.
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Sam Wrankmore
      Include steps to query and retrieve user id and password for use in other process steps that require user authentication.
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Sam Wrankmore
      Sam Wrankmore unlocked the badge Points Achiever
      Points Achiever
      Earn points on the site.
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Sam Wrankmore
      New functionality to provide both a default and custom/override timeout value or all component and process steps. Both component and application steps often override or a failure / process erro causes... them not to return. Once discovered, the only method is to cancel the process. A timeout would ensure a failure is captured and appropriate rollback or likewise process can be put in place to handle it. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Sam Wrankmore
      Sam Wrankmore added new listing User Impersonation - GUI side in SDA/Deployment Automation
      Give the ability for an Administrator to impersonate or 'log in as' another user, i.e. see SDA in the eyes of another user We need to be able to see SDA in the eyes of other users to ensure access and... permissions are granted correctly and to aide debugging problematic processes. This sort of functionality is already available in SBM and it is essential when supporting a large team and a large number of applications - that all may be configured with different permissions. GitHub Enterprise is a good example of logging user impersonation providing an audit trail of all activities. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Sam Wrankmore
      Remove the limitation of only displaying dates and times in US format - which may be confusing for non-US users Allow the selection or definition of a datetime format on a user-by-user basis. Allow t...he selection or definition of a datetime DEFAULT format on the server. We are currently subjected to viewing all datetimes in US format (mm/dd/yyyy), irrespective of the locale chosen by the user. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Sam Wrankmore
      Sam Wrankmore added new listing Security Tokens - ability to modify existing tokens in SDA/Deployment Automation
      Simplify maintenance and debugging by allowing security tokens to be modifed post creation, and provide a mechanism to view 'expired' tokens Administration | Security | Tokens Allow existing tokens... to be modified after creation such that the description and/or date can be changed Expired tokens should be moved to an inactive state that may be reviewed or deleted at a later date We use tokens to authenticate when utilising the CLI interface and as such may need to review the tokens for debugging purposes. Currently, if a token expires it is immediately deleted with no record of its existence. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Reuqest that a "Required Resource Role” be added as a main property of component and global processes. In SDA, when an application process calls a component process one may specify that the run is lim...ited to resources having a specific resource role.  I find that our workflows typically have to make assumptions about the target environment which seem to align with the resource role concept – “a resource of a given type”. May I suggest that “Required Resource Role” be added as a main property of component and global processes.  This would permit the manual “Run Process” dialog to limit the list of processes (or resources, depending on the order) that may be selected to only those appropriate to the target.  Many processes are certain to fail when run on the wrong kind of resource.  This would assist users by reducing the number of incorrect choices they could make. The setting would be optional, and if unset then the process would be available for all mapped resources. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Sam Wrankmore
        As Administrator of SDA I need to KNOW THE LIST OF USERS CONNECTED TO SDA AS ADMINISTRATOR OF SDA I NEED TO KNOW THE LIST OF USERS CONNECTED TO SDA in case of failure, if we need to restart the ser...ver or for an audit resource. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Sam Wrankmore
      Kanban is a popular method for identifying the status and priority of work items.  Typically, a visual "wall" displays the items in columns depending on whether they are "to be done", "in progress" or... "completed".  As an item changes status, it moves between the columns, enabling a viewer to quickly see not only the status of an individual item, but the overall progress of a project.  This idea would be to create a Kanban friendly interface within SBM that enables users to represent tasks as cards on a wall within columns to indicate priority and status. At a basic level, a Kanban wall looks something like this: This idea woudl be to emulate such a card wall within SBM as a view.  The view would be populated by the items in a project and the placement of the items on the wall would be goverened by their status (i.e. which column to be in) or their priority (i.e. how high up the column the item is shown).  The items can either be updated by clicking on them to "drill down" into a typical update form or by just moving/sliding them between columns which will transition the status of the item - e.g. from "To Be Done" to "Doing".  If additional information is required to move an item (e.g. the item must be assigned to be moved to "Doing"), such information will either be requested or filled in through automated rules (e.g. the person sliding from "To Be Done" to "Doing" would automatically become the owner).  Colors can also be used to supplement the interpretation of status (e.g. an item in critical status may have a red outline around it).     More
      Stream item published successfully. Item will now be visible on your stream.
  • No blogs available.

  • DateTitle
    06/03/2017 Default and custom timeout available for all component and process steps
    12/04/2016 User Impersonation - GUI side
    25/02/2016 Datetime format - allow any format required, e.g. English UK dd/mm/yyyy
    25/02/2016 Security Tokens - ability to modify existing tokens
    15/12/2015 Use LDAP authorization with SSO authentication

Recent Tweets