The document discusses pending enhancements and development schedules for System Director and SCOPE Studio. For System Director, enhancements are planned for alert frameworks, C++ patches, installation/monitoring, tablets, mandatory installations, data sync monitoring, concurrent patches, jobs, scheduling, SNMP traps, comparisons, and LDAP/ActiveDirectory. The development schedule is shown with target dates for completing enhancements. For SCOPE Studio, enhancements are planned for the Eclipse version, platform independence, pre/post hooks, transaction parameters, custom screens, mappings, widgets, jar files, and web UI customization. Branching strategies are outlined for developing future releases of System Director and SCOPE Studio in parallel with maintaining stable release branches.
1. SCOPE Studio Team
System Director and SCOPE Studio Plan
SCPP Release 2013+
Architecture, Global R&D, Manhattan Associates, Inc. Strictly Confidential. Not For Distribution.
2. System Director – Pending Enhancements
• Alert Framework Extensions
– Execution of SQL, JavaScript expression and custom Shell/command-line scripts
• Support for C++ Patches
– Apply and roll-back C++ patches
• Separating Installation and Monitoring Aspects
– Add configuration to enable either, or both, of installation/monitoring features
• System Director for Tablet
Architecture, Global R&D, Manhattan Associates, Inc. Strictly Confidential. Not For Distribution.
– Enable System Director for tablet devices; primarily iPod 4+
• Making System Director Mandatory for Installation
– Platform products should only be allowed to be installed using System Director
• Support for Data-Sync Monitoring
– For monitoring and troubleshooting data-sync activity in distributed deployment
• Support for Applying Patches to Multiple Environments Concurrently
– Ability to apply a patch to multiple environment at the same time on-demand
• Support for Configuring Jobs
– Ability to schedule recurring activities
• Support for Scheduling Installations and Patch Deployments
– Ability to install applications and apply patches at a scheduled time in future
• Support for SNMP traps
– Ability to publish/generate SNMP events that may be handled by external systems
• Ability to Compare Installations
– Pick two installations of a platform product and compare them for differences
• SD authentication using LDAP and/or ActiveDirectory
– Ability to login in SD by using an existing LDAP or ActiveDirectory credentials
3. System Director – Development Schedule
- Alert Framework Extensions
Drop 15
- Support for C++ Patches
- Separating Installation and Monitoring Aspects
2/15/2013
- System Director for Tablet
Architecture, Global R&D, Manhattan Associates, Inc. Strictly Confidential. Not For Distribution.
2013.0_CA
- Making System Director Mandatory for Installation
- Support for Data-Sync Monitoring
3/31/2013
- Applying Patches to Multiple Environments Concurrently
2013.0_WM
- Support for Configuring Jobs
- Scheduling Installations and Patch Deployments
4/30/2013
- Support for SNMP traps
2013.1
- Ability to Compare Installations
6/30/2013
- Support for LDAP and/or ActiveDirectory
(TBD)
?
4. System Director – Branching Strategy
SD 2.0 • Create a branch for SD 2.0
Release Branch development ("bleeding-edge") on
(stable) 2/15
SD 2.0
Dev Branch • Continue fixing defects in the
stable release branch
Architecture, Global R&D, Manhattan Associates, Inc. Strictly Confidential. Not For Distribution.
(bleeding)
• Continue building SD releases from
the release branch
• Continue new development in the dev
branch
2/15/2013
• Continue merging stable enhancements
in the release branch after thorough
testing
SD Repo
• Continue to involve QA as part of
the active development sprints
5. SCOPE Studio – Pending Enhancements
• Upgrade SCOPE Studio Eclipse Version to Latest
– Upgrade SCOPE Studio to use Eclipse Indigo 3.7 or Juno 4.2 (depending upon timing)
• Make SCOPE Studio Independent of Platform Release
– Make a single version of SCOPE Studio work with all platform releases (2010+? 2012+?)
• Common Pre/Post Hook for JSF Backing Bean Classes
– Required to change the return state so that custom screens can be invoked in the base flow
• Generic Method to Fetch Transaction Parameter
Architecture, Global R&D, Manhattan Associates, Inc. Strictly Confidential. Not For Distribution.
– Required to have a ON or OFF switch for displaying/hiding a custom field
• Ability to Configure Custom Screens in Menu
– Create a custom menu entry that can be configured to open custom screen
• Mapping for Identifying Screen with Functionality
– Currently the only way to find it is using the Web URL which is not very accurate/intuitive
• Mobile Designer – Application Specific Widgets
– LPN, Quantity, Location etc.; can be used to create new custom screens quickly
• Locating Jar Files Matching a Class
– Ability to find the Jar file that contains a given class
• Web UI Customization
– Ability to customize base Web UIs
6. System Director – Development Schedule
2013.0_CA
- Upgrade SCOPE Studio Eclipse Version to Latest
- Make SCOPE Studio Independent of Platform Release
3/31/2013
- Common Pre/Post Hook for JSF Backing Bean Classes
- Generic Method to Fetch Transaction Parameter
Architecture, Global R&D, Manhattan Associates, Inc. Strictly Confidential. Not For Distribution.
- Ability to Configure Custom Screens in Menu
- Mapping for Identifying Screen with Functionality
- Mobile Designer – Application Specific Widgets
- Locating Jar Files Matching a Class
?
- Web UI Customization
(TBD)
7. SCOPE Studio – Branching Strategy
SS 2.0 • Create a branch for SD 2.0
Release Branch development ("bleeding-edge") on
(stable) 3/31
SS 2.0
Dev Branch • Continue fixing defects in the
stable release branch
Architecture, Global R&D, Manhattan Associates, Inc. Strictly Confidential. Not For Distribution.
(bleeding)
• Continue building SS releases from
the release branch
• Continue new development in the dev
branch
3/31/2013
• Continue merging stable enhancements
in the release branch after thorough
testing
SS Repo
• Continue to involve as part of the
active development sprints