Solution Manager Overview with notes pages

1. I N F O R M A T I O N D E P L O Y E D . S O L U T I O N S A D V A N C E D . M I S S I O N S A C C O M P L I S H E D .
Web Based Supply Chain Management
Solution Manager (SolMan) 7.2
Solution Documentation (Sol Doc) Overview Training
May 9, 2018
ALM and OCM Teams
1/7/2020
1

2. Meeting Agenda
 Goals and Objectives
 Process Overview
• Solution Documentation Overview
• Process Management Overview
• Key Terms and Concepts
• SolMan 7.1 & 7.2 Deltas
• Roles and Responsibilities
 Review or Demo
• Log into SolMan 7.2 and access Sol Doc
• Sol Doc Navigation
• Lookup / Search for a Document
• Create a Document
• Edit a Document
• Advanced Topics
 Support and Resources
 Q and A
2
1/7/2020

3. Goals and Objectives
 Describe Solution Documentation concept and functions
 Describe SolMan Process Management concept
 Describe the versioning process in Sol Doc
 Describe Sol Doc integration with other SolMan components
 Define major differences between SolMan versions 7.1 and 7.2
 Describe key terms and concepts
 Log into SolMan 7.2, navigate within Sol Doc, and look up documents
 Describe how solution documents are stored and organized in SolMan
7.2
 Create and edit documents, and know other new features and
functionality available within SolMan 7.2
1/7/2020
3

4. 4
What is Solution Documentation
 A hierarchical structure of all XXXX solution documents;
serves as the single source of content
 Tracks and manages version control of all solution
documents including final/production version
 With SolMan 7.2, Sol Doc is more integrated with:
• Technical Bills of Material (TBOMs)
• Business Process Change Analyzer (BPCA)
• Change Request Management (ChaRM)
 Previously called Business Process Hierarchy
• Contains Business Processes, Business Process Steps and
Attributes including TBOMs
1/7/2020

5. 5
What is Solution Documentation, (continued)
 Sol Doc uses a hierarchical structure to store and maintain business
processes and associated documentation
MainSolution
System
Landscape
(and
applications)
Processes
and Libraries
Branches
(Versions)
Sites
Developments
Roles
Sol Doc is organized into the following
different areas:
• Libraries of reusable documentation for
technical objects, such as development
objects, executables, and configuration
activities
• Library of business process steps where
documentation can be used from the
other libraries
• Library of interfaces where interfaces
used by end to end processes are
documented
• End to End Business Processes where
scenarios and processes are modeled by
reusing the process steps, interfaces, and
technical objects from the libraries
In detail, these areas of the Sol Doc model provides the following features:
• Developments and Executables Library
• Component‐oriented container of technical objects and their documentation, e.g. Web Dynpro
applications, transactions, custom reports etc.
• Technical objects can be reused in different process steps and end‐to‐end processes
• Libraries can be partially automatically generated based on usage statistics and structured by the
application component hierarchy (ACH)
• Process Step and Interface Library
• Function‐oriented container of all process steps and their business‐context independent documentation
• Process steps can be reused in different end‐to‐end processes
• Automated, on‐demand generation of the library structure based on the ACH, which can be manually
extended
• Configuration Library
• Function‐oriented container of configuration activities, grouped into reusable units
• Configuration units can be reused for repeated configuration tasks
• End to End Processes
• Business‐oriented documentation of processes describing XXXXs end‐to‐end scenarios
• Library elements, e.g. process steps, interfaces and technical objects, can simply be reused
1/7/2020

6. 6
What is Solution Documentation, (continued)
 Sol Doc automatically attaches a new version number to a document
after a maintenance or enhancement release
SolMan provides change control management for documents by:
• Adding a unique identifier to SolMan document attributes
• Introduces a release strategy with electronic signatures for signed out documents
• Automatically attaches a new version number to a document after release
Planning
Installation
Qualification
Operational
Qualification
Performance
Qualification
Validation
Report
User
Requirement
Specification
Functional
Requirement
Specification
Systems Design
Specification
Development
1/7/2020

7. Process Management
 Process Management keeps business processes and systems
synchronized using two key applications
• Solution Administration (Sol Admin): Provides an overview of all
process and solutions connected through interfaces.
− Administrators utilize the Sol Admin transaction to maintain XXXX
processes and systems
• Sol Doc: Provides a common directory for business processes
and associated documentation (.exe files, business
requirements, testing documents, etc.).
− Business analysts, process modelers, and the functional team use
Sol Doc to review, update, and store all project‐related elements
1/7/2020
7

8. 8
 Sol Doc
• Web‐based documentation
experience
• Integrated BPMN process editor
• Multi‐level hierarchies
• Processes assembled from reuse
libraries
• Processes are validated and
optimized continuously based on
real usage
 Integrated process experience
• Business Process Monitoring
integrationIntegrated graphical Business Process
Model and Notation (BPMN) process editor
Process Management, (continued)
1/7/2020

9. 9
Process Management, (continued)
 Reuse avoids redundant documentation
1/7/2020

10. 10
Key Terms and Concepts
Terms Definition
Solution
Documentation (Sol
Doc)
• The solution is the sum of XXXX’s systems, applications, and
processes. It acts as a container for versions of solution
documentation, one of which is the production version.
Solution • The sum of XXXX’s systems, applications, and processes.
• Processes – covers all XXXX business processes.
• Systems – covers all production systems that are
connected through interfaces.
System Landscape • Comprised of all XXXX systems in the Landscape Management
Database (LMDB).
• Uses logical grouping for business processes and libraries.
Branch (including
production branch)
• A branch represents a version of the solution documentation
containing processes, libraries, applications, and systems.
• A branch always collects all content of its parent branch. The
same element has always the same identity in all branches. As
a result, all changes released into e.g. the production branch
become automatically visible in all child branches.
1/7/2020

11. 11
Key Terms and Concepts, (continued)
Terms Definition
Logical component
group
• A logical component group (LCG) is a high level view of an
application. It is a group of logical systems of a type, for
example, Portal, BI, CRM, SRM, etc.
• Used to depict the execution runtime of, for example, process
steps.
• The LCG is a release independent placeholder for concrete
systems.
Logical component • A logical component (LC) refers to the concrete technical
systems of a system track typically belonging to the same
transport landscape and having the same product version.
• The technical systems assigned to logical components are
classified according to their system role (i.e., Development
system, Quality Assurance system).
System role • Determines which system to use for various operations.

12. 12
Key Terms and Concepts, (continued)
Terms Definition
Lifecycle based on
Branches
• A branch represents a version of the Sol Doc containing
processes, libraries, and systems.
• Production branch – represents the productive version of the
entire Sol Doc.
• Maintenance branch – represents the editable version of the
productive Sol Doc and provides a safe environment for
performing changes.
• Development branch – represents the development version for
future Sol Doc.
Library • Collection of reusable objects that can be referenced from Sol
Doc to avoid duplicate content and reduce maintenance
effort. Some objects include:
• Executables
• Development
• Configuration
• Business Processes
• Process steps
• Interfaces
1/7/2020

13. 13
Key Terms and Concepts, (continued)
Terms Definition
Development Library • A functional oriented collection of re‐usable development
object originals to document executable customer
enhancements.
• Automatically grouped by logical component groups on the first
level and on the following using the applications component
hierarch or development package.
Configuration Library • A functional oriented collection of re‐usable configuration
units used to describe the configuration of single functions,
complete applications, or processes.
• Grouped by functional domains that correspond to org
structures.
• Organized according to a process org.
Interface Library • A functional oriented collection of re‐usable interface
originals used to depict how system breaks are bridged.
• Organized according to scenario and functional aspects and
follows operational needs.
1/7/2020

14. 14
Key Terms and Concepts, (continued)
Terms Definition
Process Step Library • A business oriented collection of re‐usable process step
originals used to assemble processes.
• Grouped by functional domains that correspond to org
structures.
• Should exist only once to obtain an overlap‐free library
structure.
Executable Library • A functional oriented collection of re‐usable executable
originals used to facilitate process step originals with
execution means.
• Calculated using managed system usage data.
• Automatically grouped by logical component groups on the first
level and on the following using the application component
hierarchy or development package.
TBOM • Technical Bill of Materials. Includes all objects required to
complete an activity on the XXXX system.
1/7/2020

15. 15
Key Terms and Concepts, (continued)
Terms Definition
Executable • Executable objects used to perform certain tasks.
Element • Term for structure nodes and object list items.
View • Views are the visible scope of solution. User roles enable
specific views of SolMan.
Scope • Sol Doc scope displays view definitions and additional filter
criteria. Scopes can also be used to review generations of
process documentation and for report execution.
Report • Provides statuses of Sol Doc (completeness of documents,
assignments, objects).
• Reports can be defined and executed based on existing XXXX
reports.
1/7/2020

16. Key Terms and Concepts, (continued)
Capability Features
Usability • Modern browser‐based user interface which makes the administration
and documentation of the solution simple, intuitive, and business‐
focused.
Context‐driven user
interface
• Simple access to add new elements.
− Use the right mouse button at the location for a new element
− Context menu offers all of the functions that are allowed at the
selected location of the element
Implicit Save of user
entries
• Entries do not need to be saved by the user.
− Every change of an element is saved automatically when another
element is selected
− Offers a “Save” button to manually save work
Re‐Use • Allows users to organize reusable documentation to reduce content
management for multiple use in different end to end business processes.
− Business process steps
− Transactions
− Development objects
− Configuration activities in libraries
1/7/2020
16

17. Key Terms and Concepts, (continued)
Capability Features
Integration • Single source of truth for all content related to business processes.
• Supports all application lifecycle phases from implementation through to
operations.
Versioning • Simplifies maintenance, new development and upgrades using the
version concept – branches.
1/7/2020
17

18. SolMan Deltas
 Major differences between SolMan 7.1 and 7.2 include:
• New user interfaces
• Improved integration between Sol Doc and other SolMan tools such
as:
− ChaRM
− BPCA
− Technical and Business Process monitoring
• Major aspects of 7.2 are context driven including:
− Search
− Right‐click Menu
 SolMan 7.2 Supported browsers include:
• Mozilla Firefox
• Google Chrome
• Apple Safari
• Microsoft Internet Explorer IE11
1/7/2020
18

19. 19
Sol Doc – User Interface
 Users can access Sol Doc from the SAP SolMan launchpad or via the link
from the Solution Administration user interface
SolMan
Launchpad
SolMan SAP GUI
User Interface
• SolMan User Interface
• Familiar interface to SolMan.
• SolMan Launchpad
• In the upper part the structure elements are shown in a column browser. The first column
contains the 2 top folders for the Business Processes data and the Libraries. On selecting one of
those the second column gets visible containing the children of the selected top folder: Folders,
Scenarios, Master data, and Organizational Units.
• For each selected element, the lower part of the UI lists all elements assigned to the selected
structure element. The bread crumb above the column browser always shows the path to the
actually selected structure element and also provides a navigation functionality to a parent
element within this path. The right part of the UI shows the attributes of the selected element.
• The Sol Doc structure in the Browser is also available as graphic: in the context menu of each
structure element the action Open Value Chain Diagram provides the switch from column
browser approach to graphical representation.
Project and Process Management My Business Requirements – Provides an overview of business
requirements for the user based on user role and includes the following tiles.
• Sol Doc: The single and central point of access for all Sol Doc content.
• Solution Administration: Provides and overview of XXXX solutions.
• Scope and Effort Analyzer: Used to analyze the scope of activities prior to maintenance, enhancement,
and support pack deployment.
• Requirements Management: Used to maintain change processes for XXXX.
• My Projects – Project Management: Provides an overview of all projects the user is responsible for.
• My Tasks – Project Management: Provides and overview o project tasks for the user.
1/7/2020

20. 20
SolMan – Roles and Responsibilities
Role Role Responsibilities Assignment
Admin • Accessing the Implementation work center
and the SAP Fiori‐embedded launchpad
− Setting up the framework for process
documentation
− Editing road maps as required
− Editing system landscape information as
required
− Setting up training materials framework
− Using cPro integration
‐ ALM Team
Execution • Accessing the Implementation work center
and the SAP Fiori‐embedded launchpad
− Editing process documentation
− Displaying system landscape information
‐ Functional Team
Display • The display user for process management is
allowed to display all activities in the process
management
‐ All XXXX Team
Members
Admin
• Maintains the system landscape and user roles.
• Adds and removes systems.
• User roles are maintained by Administrators and control what a user can view, edit,
create in Sol Doc.
1/7/2020

21. 21
Sol Doc – Admin View
XXXX Solution
for Sol Docs
Solution
Administration
tabs
Maintenance links
Logical Component
Groups
Site (Global)
Technical systems
Branches
 Admin users can display and maintain technical details for Sol Doc
Admins use the Solution Administration transaction to define and maintain the following
components:
• Solution Administration tabs
• System Landscape Tab: Includes the assigned logical component groups to
system landscapes.
• Change Control Landscapes Tab: Used for Change Request Management.
• Document Types Tab: Includes all document types stored in SolMan and are
used in the Knowledge Warehouse.
• Imports Tab: Allows users to upload SAP best practices and business process
content.
• Properties Tab: Users can view the current solution.
• Maintenance Links
• Maintain Logical Component Group: Used to maintain the branches for the
hierarchical structure in SolMan (SAP_EP_PORTAL, SAP_ERP_ECC, SAP_PI).
• Maintain Sites: Used to maintain the sites for each branch (Global).
• Assign Technical Systems: Used to maintain the technical systems assigned to
branches (ED1, ENJ, EPJ)
1/7/2020

22. Demonstrations
1. Log into SolMan 7.2 and access Sol Doc
2. Sol Doc Navigation
3. Lookup / Search for a Document
4. Create a Document
5. Edit a Document
6. Advanced Topics
1/7/2020
22

23. Demonstration
Log into SolMan 7.2 and access Sol Doc
1/7/2020
23

24. Log into SolMan 7.2
 Discuss different methods to access SolMan 7.2
 Review different branches in the SAP GUI launchpad
 Select the Sol Doc tile in the SolMan dashboard
 Discuss the Main Solution screen
Detailed Step‐by‐Step Work Instructions with Field‐level descriptions are available
on the XXXX PMO Portal using the following link:
SolMan 7.2 Training
(https://aide.XXXX.net/ocm/Documents/Project Team Training/SolMan 7.2)
1/7/2020
24

25. SolMan 7.2 Login
 Workcenter URL for MD1 (DEV):
 MP1 link (PROD): Alternative access via SAP GUI in
MD1/MP1:
• SM_CRM to access ChaRM
• SOLDOC to access the Sol Doc component
• SM_WORKCENTER or SOLUTION_WORKCENTER to access the
SolMan Workcenter
 To access SolMan 7.2 Web UI or SAP GUI, users will need
NITC VPN access
1/7/2020
25

26. 26
Access Sol Doc from the SAP GUI User Interface
SolMan Instances
 Most users are familiar with accessing SolMan from the SAP
GUI User Interface
1/7/2020

27. 27
Access Sol Doc from the SAP GUI User Interface
SolMan
Launchpad
 The SolMan dashboard offers all applications the user is
assigned to based on their role in the system
1/7/2020

28. 28
Review the Main Solution Screen
 Provides the overview functions, display of the different
views, and how they interact
Folder Structure
Branch and
System Options
Elements
Breadcrumbs
Attributes
View Options
• Branch: Select dropdown
menu with quick info Branch in
the header.
• System Role: Select dropdown
menu with quick info System
Role in the header.
• Branch: Select dropdown menu with quick info Branch in the header (visible is the name
of the currently selected branch). A list with all branches created for the selected
solution is displayed.
• Site: Select dropdown menu with quick info Site in the header (visible is the name of the
currently selected site). This dropdown menu is only available if the selected branch is
site enabled.
Note: Only admins will see the Site option.
• System Role: Select dropdown menu with quick info System Role in the header (visible is
the name of the currently selected system role). If your branch is newly created or you
are accessing an existing branch for the first time, the default system role is displayed.
The name of the selected system role is displayed in the header.
1/7/2020

29. Demonstration
Sol Doc Navigation
1/7/2020
29

30. Sol Doc Navigation
 Discuss the library structure
 Navigate through all key elements and objects
 Look up a document by browsing through the libraries
 Review breadcrumbs, tabs, links, views
 Discuss the Elements pane
 Review the Attributes pane
1/7/2020
30

31. 31
Display and Maintain Sol Doc Content
 Provides several ways to display and maintain the Sol Doc content
• Users can switch between the browser and list representation of the data.
• Utilizes integrated search, where‐used, and reporting functionality.
Note: While the browser and list representation are always selectable, the search, where‐used, and
reporting result lists are only available after the functionality behind is triggered by the user.
User
Navigation
Panel
Hierarchy
Structure
Results
Panel
Attributes
Panel
• Explain the folder structure (Business Processes versus Libraries).
• Explain the breadcrumbs to navigate.
• Review the attributes panel on the right.
• Describe the types of documents, etc. in the bottom pane.
The List Representation of the Sol Doc Content
The list representation mode displays the elements within the sub‐tree of the selected structure element as a flat list.
Options
• View: Select dropdown menu with quick info View in the header (visible is the name of the currently selected view).
• History: The dropdown menu History contains a list of elements that have been selected recently (the latest selected
elements come first). A structure element is added to the history if it is selected in the browser view only. The history
can be cleared via Global functions menu, item Settings, option Delete navigation history.
• Favorites: The dropdown list Favorites can be used to navigate to elements that have been added as favorites.
• Back in History: The Back button is located at the left hand side of the header. It allows the user to navigate one step
back in the history list. When choosing Back the latest entry in the history list is deleted. If the history list is empty, the
button Back is inactive.
• Bread Crumb: The bread crumb is displayed in the lower area of the header and is available for the Browser, List, and
Search Result view. It contains all selected structure elements including the root element Solution. In browser and list
view, the bread crumb can be used for navigation and displays the navigation path to the last selected structure
element. In search result view, the bread crumb displays the search path from the last selected structure element. In
case of multiple selection of structure elements, only the first element from the selected elements will be considered
for display.
1/7/2020

32. 32
Display Elements in Sol Doc
 Provides all elements within the sub‐tree of the selected
structure element (also visible in the bread crumb) as a flat
list Breadcrumb
Content displays
in a browser
representation
Users can search for documents using folders and breadcrumbs.
1/7/2020

33. 33
Browse Sol Doc Branches and Elements
 If a branch is newly
created or if the user is
accessing an existing
branch for the first time,
only the first column of
the hierarchy displays
 Otherwise, the browser
displays the last selected
element in the hierarchy
Sol Doc Hierarchies
• Sol Doc provides lifecycle versions for the process structure, the attributes and the
Knowledge Warehouse documents. This versioning mechanism is based on branches. A
branch is a versioning context in which the Sol Doc may be maintained, developed
further or adapted and has the following main features Each solution has a production
branch context.
• A branch may have one or more child branches which can be used as separate
versioning contexts. The changes done in a child branch may be brought back to its
parent branch by a release operation for the changes.
• A maintenance branch can be defined as a single special child branch of the production
branch.
• If a maintenance branch exists for a production branch then the production branch
version is locked for changes and thus cannot be modified directly. In this case the
production branch version can only be changed via a release of the maintenance branch
or a release of another child branch. Although the production branch version may not be
edited it can be displayed in the Sol Doc.
1/7/2020

34. 34
Review Elements, Attributes, List Panels
 The link List is highlighted by default
• Two panels display (list and attribute)
The list displays
elements found
in the hierarchy
under the last
selected branch
Attributes and
assignments for the
selected element
display in the
attribute panel
Users can resize or
collapse the list panel
All other links are displayed standard. The splitter between list and attribute panel is
displayed. Resize or collapse the splitter to the right. The elements are displayed in a list.
Only those elements are displayed which are found in the hierarchy under the last selected
structure element. The last selected element is also displayed in the list and is explicitly
selected. The attributes and the assignments for the selected element are displayed.
1/7/2020

35. 35
Review Elements, Attributes, List Panels (continued)
 Use the horizontal and vertical scrollbars to display additional details in
the Main Library, Elements, and Attributes panes
Vertical scrollbar
Horizontal scrollbar
1/7/2020

36. 36
Display Global Functions and Solution Options
 The Global functions menu contains options for Sol Doc Global functions
menu icon
Solution options
1/7/2020

37. Demonstration
Lookup / Search for a Document
1/7/2020
37

38. Look Up a Document
 Look up a document by using the search functionality in Sol
Doc
 Discuss how location in Sol Doc affects searches
 Open a document in Sol Doc
Users can search for objects including:
Executables, Test Cases, TBOMs to view and
modify, as appropriate. It is strongly
recommended that all users search Sol Doc prior
to creating new documents to reduce duplicate
files; use advanced search functions, as needed
1/7/2020
38

39. 39
When the search is executed,
the user interface switches to
the Search Result mode and
shows the list of hits related to
the search term
The search is restricted to the
sub-tree of the selected
structure element visible in the
bread crumb
Basic Search
 Trigger a basic search within Sol Doc by entering a search
term in the input field on the upper right part of the user
interface
1/7/2020

40. Basic Search, (continued)
 Sample document for transaction MMBE
Click on a
document link to
open in a new
browser window
1/7/2020
40

41. Basic Search, (continued)
The document opens in a
new browser window
Attributes for
the document
1/7/2020
41

42. Demonstration
Create a Document
1/7/2020
42

43. Create a Document
 Open options to create a new document
 Discuss document options
It is strongly recommended that all users
search Sol Doc prior to creating new
documents to reduce duplicate files; use
advanced search functions, as needed
1/7/2020
43

44. Create a Document
Right-click anywhere in
the Elements section to
display the options for
creating, changing, or
viewing documents
Documentation options
 Right‐click anywhere in the Elements section to create a new
document
1/7/2020
44

45. Demonstration
Edit a Document
1/7/2020
45

46. Edit a Document
 Right‐click anywhere in the Elements section display edit
options for a document
 Discuss edit options
 Check out a document
 Make changes
 Check the document back in
 Review attributes for the document
1/7/2020
46

47. Edit a Document
Right-click on a
document to display
options available to
edit a document in
Sol Doc
 Right‐click on document
• context menu will now show edit options
Document attributes
1/7/2020
47

48. Advanced Topics
 The following slides describe additional features available in
Sol Doc, including:
• Advanced search options
• Filter options
• Personalization options
• Drag and drop feature
• Where Used List
• Report options
1/7/2020
48

49. 49
Advanced Search
 Available via the dropdown menu of the search icon
• More detailed search criteria can be defined to narrow results
• System saves the searches so they can be accessed later
Search
icon
1/7/2020

50. 50
Advanced Search (continued)
• Use a combination of search
filters as appropriate
• Search filters that have an
associated list of values
display (the Matchcode
icon) in the field
• Use the (the Search icon)
to execute the search
• Results display based on the
search criteria
Results
List
List of
Values
icon
Search
icon
1/7/2020

51. 51
The Filter Panel in Sol Doc
 On the left part of the UI there is a filter panel which can be expanded
and collapsed; filters can be set from any Sol Doc screen and will remain
open until the filter is modified or collapsed
Filter icon
Filter pane
Filter options
Filter result
options
1/7/2020

52. 52
The Filter Panel in Sol Doc
 The filter panel offers the possibility to switch into a different layout
providing a defined set of columns and filter aspects
 The user can also change the current layout by adding filter aspects or
filter the visible data by setting filters within a filter aspect
 In the browser UI mode the filters as well as the statistical information is
only related to the assigned elements of the selected structure element,
but not towards the structure part in the column browser
Filtered results
Filter pane
1/7/2020

53. 53
Personalization of Selected Layouts
 The layout (visible columns and selected filter aspects) used
within Sol Doc is personalized
• The actual layout personalization is stored user dependent for all
modes of the Sol Doc screens except reporting
• At restarting the Sol Doc screen, the last used layout is loaded automatically. The last up
to 10 used layouts are provided as last used list in the layout dialog drop down in the
expandable filter panel area of the screen. Additionally, the default layout is always
available within the drop down list. An entry More… within the layout drop down
provides a search functionality to switch into all available layouts. This is affects all
public layouts as well as private layouts for the current user.
• As the layouts to display a report result are report specific, for each single report result
the selected layout is personalized to show the result at the next execution of the
report. The layout drop down provides all available layouts for the current report, not
only the 10 last used ones. For this reason no More… function is needed in reporting.
1/7/2020

54. 54
Drag and Drop Documents
 The drag and drop function offers the possibility of creating
and updating documents by uploading files from the user’s
computer using drag and drop.
• In the maintenance branch of a solution, users can display and
hide a drop area for drag and drop of one document or many
documents
• This allows the upload of documents and the upload of new
versions of documents. During the upload, users can perform
the following mass changes:
− Change proposed document names
− Create and update documents
− Document type selection
− Assignment to documentation or test group
The Sol Doc offers a dedicated area where users can drop files from their computer.
This area is hidden by default and can be shown on request using Show Drop Area of the menu Global functions.
Note: The drop area is only available in the Browser view of the Sol Doc.
• When accessing the Sol Doc for the first time, no drop area is displayed and the menu Global functions contains
the entry Show Drop Area.
• When choosing Show Drop Area, the drop area is displayed at the bottom of the screen, below the assignment
list.
• When choosing Hide Drop Area, the drop area is hidden again.
• The next time the user accesses the Sol Doc, the drop area is displayed or hidden corresponding to the last choice
in the Global functions menu.
The drop area is never shown in the views List, Search Result, Where Used List and Reporting. In these views, the
entries Show Drop Area and Hide Drop Area of the menu Global functions are disabled. If the Sol Doc is in read‐only
mode, the drop area is not shown. For example, the drop area is not shown in the production branch, as this branch
is read‐only.
Users can drop files from their computer into the drop area. For example, with a Microsoft Windows computer, drag
files from the desktop or from the file explorer and drop them into the drop area of the Sol Doc. When dropping files
from the users computer into the drop area, the dialog Upload Documents is displayed in the Sol Doc.
In the dialog Upload Documents, users can specify the information for the documents to be created or updated from
the dropped files.
The following fields are available for each dropped file:
• file name (read‐only)
• document name
• document type
• element type
• action
The topmost row of the dialog allows mass maintenance for the fields Document Type, Element Type and Action of
all files. The proposed Document Name is the file name without extension (for example: Sales if the dropped file was
named Sales.docx. The values offered for the field Document Type comply with the document types in the scope for
1/7/2020

55. XXXXs solution. Check the document types for XXXXs solution in solution administration on tab
Document Types.
1/7/2020
54

56. 55
Drag and Drop Documents, (continued)
 The values proposed in the dialog Upload Documents for the
dropped files depend on the available documents under the
selected Sol Doc element
• Once a file is added, users can choose the values for document
type and element type in the Upload Documents dialog
• If users add a URL shortcut into the drop area, the proposed
value for the field Element Type is Document URL
For values offered for the field Element Type, there are the following rules:
The values comply with the element types allowed for the creation under the currently
selected Sol Doc element (compare with the element types offered in the context menu of
the assignment list for the selected element).
• The values comply with the configuration of the document type administration for the
selected document type. Check this in solution administration, menu Global Functions in
Document Type Administration by selecting the corresponding document type. In the
tab Usage, see under which element types a document or a test document of the
selected document type can be created.
• The element type Document URL is only offered for dropped URL shortcut files.
For the field Action, the value Create is always available. The value Update is only available
for files having a name and file type matching an existing document of the selected
element. For example, if the user drops the same file a second time under the same Sol
Doc element, the action Update will be available for this file.
Drag and Drop
• Leave the proposed document name unchanged and press OK.
• If a user drops the same file into the drop area again, the proposed action is Update and
the values for document type and element type correspond to the ones selected when
the file was uploaded for the first time.
Creation and Update of Documents
• The OK button in the dialog Upload Documents, uploads the dropped files and the
corresponding Sol Doc documents are created or updated matching the input provided
for their fields.
1/7/2020

57. • A progress bar is displayed during the upload process. A success message is displayed
after creating or updating the documents.
1/7/2020
55

58. 56
The Where Used List
 For all element types which can be referenced from elsewhere
in the solution documentation, the context menu offers the
action Where Used List
• All library types (executable originals, process step originals etc.),
documents or processes can be used multiple times
Right-click an object
to select the Where
–Used List feature
When the Where Used List
is requested by the user,
the result is loaded and the
active UI mode switches to
display the Where Used List
1/7/2020

59. 57
The Reporting Result in Sol Doc
 In the Global Functions dropdown list, select Report to execute
reports from within Sol Doc
Note: After executing a report the User Interface (UI) mode switches to
Reporting.
1/7/2020

60. Support and Resources
 SolMan 7.2
1/7/2020
58

61. Support and Resources, (continued)
 SolMan 7.2 Training Materials
1/7/2020
59

62. Questions
1/7/2020
60