Profile | ebiexperts
 

Documentor Guide

WIP Introduction #

WIP: Your Work-In-Progress Management Solution. Copyright © 2001-2017 by QVAuctor Ltd. All Rights Reserved.

WIP Lifecycle Management

WIP manages and controls all aspects of a file throughout its lifecycle, from its requirement to retirement.

Whether you are a business user, analyst, developer or administrator within the system, WIP ensures you are in complete control of your work at all times.

Change Lifecycle

  • Change Request Lifecycle Management
  • Collaboration & Notifications
  • User Work Assignments
  • Agile Release Management

Source & Quality Control

  • Change Control Management
    • Version Management, Comparisons
    • Data Lineage and Impact Analysis
  • Quality Management
  • Complexity Analysis (Qlik)
  • Publication Management

Admin Control

  • Central Administration Management
  • Governance Management
  • Audits

 

Yes No

Disclaimers #

No part of the Computer Software or of this Document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, without permission in writing from ebiexperts. The information in this document is subject to change without notice.

If you find any problem with this documentation, please report it to ebiexperts in writing at support@ebiexperts.com.

ebiexperts does not guarantee that this document is without errors.

Copyright ©2017 QVAuctor Ltd, ebiexperts

The copyrighted products, product concepts, designs and design methods contained or described in this work are confidential. This work, either in whole or in part, may not be copied, reproduced or disclosed to others or used for purposes other than that for which it is supplied, with-out the prior written consent of QVAuctor, or if any part hereof is furnished by virtue of a con-tract with a third party, as expressly authorised under that contract.

Under international copyright laws, neither the documentation nor the software may be copied, photocopied, reproduced, translated or reduced to any electronic medium or machine-readable form, in whole or in part, without the prior written permission of QVAuctor Limited, except in the manner described in the software agreement.

Qlik®Tech and Qlik®View are registered trademarks of QlikTech International AB

Microsoft, MS-DOS, Windows, Windows NT, Windows 2000, Windows 2003, Windows XP, Windows Vista, SQL Server, FoxPro, Excel, Access, MS Query, Visual Basic Logo and other names of Microsoft products referenced herein are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

ORACLE and SQL*Net are trademarks of Oracle Corporation.

SAP®, Lumira, Webi, Business Objects logo, and WebIntelligence, Business Objects, Crystal Reports and other SAP® Products are trademarks of SAP Corporation.

Although QVAuctor Ltd. makes every effort to ensure that this information is accurate, QVAuctor LTD. will not be liable for any errors or omission of facts contained herein. QVAuctor reserves the right to modify specifications cited in this document without prior notice.

All other product and company names mentioned herein are the trademarks of their respective owners.

Copyright ©2017 QVAuctor Ltd, ebiexperts is a trademark of QVAuctor Limited

All Rights Reserved

Yes No

Login #

WIP provides three license types:

Admin Users

  • The user can act as an administrator and modify the options and parameters of the software. An administrator can also be a developer

Development Users:

  • User license which can be assigned full rights and access to full capabilities of the software but cannot modify the options and parameters of the software

Business Users/Analyst:

  • User license which can be assigned limited rights
  • User can access track and monitor their own Kanban board and issues
  • User can collaborate with other users
Yes No

Login #

All users are required to log into the system.

A username and password is required for login.

The login mode depends of the Plugin you are login against, for Qlik, login can be achieved by entering a WIP assigned user or WindowsAD integrated user authentication which would be integrated to your existing active director or LDAP directory. For Plugins like SAP then all SAP Analytics login modes will be available.

If your organisation is running Active Directory (AD), then it is very likely that WIP has been integrated to this system and you can use the same username and password you use to sign into your own domain or computer. The username will take the format of: domain\username

Please contact your system administrator should you have a license assigned and your login is not working or request access via the login page.

Yes No

Request Access #

Users can request access to the WIP application by filling out the “Request Access” form.

In the Login Screen click on “Request Access” button to open the form.

Note: The user is not able to set up User Rights as only an Admin Use can set up rights for a user.

Yes No

Fill out the user access form #

Fill out all the required fields in the user access request form and submit the form.

  • Name:
    • The name of the User
    • The user name is generally in the form “Domain\User” for QlikView (AD) or “User Directory\User” for Qlik Sense. Generally, this would be the same format you would use to access a windows machine on a company domain
    • This should be assigned correctly, and informed, by the system administrator
  • Password:
    • The password to be utilised.
    • The password field is used to login using the password method
    • For Qlik Sense once logged into WIP, the “User Directory\User” string will be sent to Qlik Sense and if the certificate provided is ok then the connection will be established
  • Confirm Password:
    • Repeat the password
  • Description:
    • A brief description about the User.
    • It would be good to inform the Admin user, who will approve your access application of who you are and what your role is within the organisation.
  • Email:
    • A valid email address of the User, email is required to receive notifications
  • Phone:
    • Phone number of the User, for reference only
  • Employee Number:
    • Employee number of the User. This will allow the admin user to find the user on the user directory and validate the user
  • Business Unit:
    • Click the drop down and select on or multiple Business Unit(s)
    • Business Units are set up by the administrator user so if your business unit does not exist please contact the admin users
    • Business Units are very important as users are assigned to business units and become visible when a user selects that business unit i.e. if a user wishes to assign an issue to a user, the user will be visible under the business unit selected by the user
  • Validate User:
    • Users require admin users to validate that they can attain access to the system. If you need to be validated, then check this box
    • Checking this box will send a user request task to the central administrator’s user access request dashboard from which they can action the request
Yes No

Select Workspace #

When you log in as a developer you will be requested to select both a product as well as a Workspace. A workspace will define where your files will go when you check your applications in/out.

When you select a product such as Qlik Sense or QlikView the Workspace you are able to select will filter based on your access rights to such workspace so if you don’t have the rights to access a workspace it will not be on the list to select. Should you require access to a workspace which is not on the list please contact your administrator.

Select your Workspace and click Continue

Yes No

BOARDS: Kanban Board #

The Kanban board is a central management board for all agile development of issues requested by both developers and business users. The objective of the Kanban board is to ensure requestors, and interested stakeholders, of issues thus development work, are in sync with the developer performing the work. The Kanban board and issue properties such as tasks, comments and notifications ensure development and collaboration between development requestors and developers are managed efficiently.

The Kanban board structure is both vertical and horizontal.

Horizontal movement across the board follows a process of work that takes issues from your To-Do across the board to Done statement. Horizontal movements can be both right and left so issues can move from In-Process state to On-Hold state based on waiting periods and so forth.

Vertical movement across the Kanban board moves issues from the DEV environment as releases to QA/UAT environment and publishing files from the QA/UAT environment to the PRD environment.

The Kanban board provides integrated issue migration actions that will perform actions on your issues when they are dropped into the specific area in the Kanban.

Yes No

Kanban Filters #

Kanban filters enable the user to quickly cut through the Kanban board and concentrate only on their own issues, or issues specifically aimed at a certain business user of by issue type.

Yes No

Issue Filter #

The following Issue Filters are available:

  • My Issues
    • My Issues will reflect all issues which have been assigned to you
  • Reported By Me
    • Reported By Me will reflect all issues that you have reported
  • Subscribed To
    • Subscribed To will reflect all issues that you are subscribed to as an interested party
  • Recently Updated
    • Will reflect all the recently updated issues
Yes No

Business Unit Filter #

You can filter by clicking on the Select Business Unit dropdown and selecting a Business Unit, the Kanban board will filter all the selected business unit’s issues on the board.

Yes No

Issue Type Filter #

You can filter by clicking on the Issue Type dropdown and selecting an issue type, the Kanban board will filter all the selected Issue Type issues on the board.

Yes No

Cancel Filter Selection #

When you have used a filter, the x will appear on the dropdown list, you can cancel your filter by clicking on the x.

Yes No

Create New Issue #

You can create a new issue by clicking on the Create New Issue button. This will bring up the issue form from which you can create you issue by filling in all the information.

Yes No

Create an Issue #

The WIP system enables users to create issues without requiring a license to access the system. Unlicensed users can create issues, but are unable to access, track and monitor, attach files and attachments, and collaborate with developers around the issue.

  • Reporter
    • Reporter is the person who has identified the issues with the file and wishes to have them corrected.
  • Reporter email
    • It is recommended to enter your work email on the issue as the developer may have some questions and would then be able to reach you when required.
  • Issue Name
    • Provide a suitable name for your issue. This will allow the developer to understand what your issue is about before going into the detailed description and tasks.
  • Issue Type
    • Select your issue type
    • Error Correction:
      • Error correction is used for errors within the application/file. Errors are generally data validation, incorrect rule, objects new working and would have an adverse effect on the usage of the file
    • Improvement
      • An improvement would be requested when the user wishes to improve an existing feature, view, calculation or visualization object.
    • New Feature
      • A new feature request can be done for any new file creation requirements, or when something does not already exist within the files and you wish to add something new to the file.
    • Description
      • Provide a suitable description for your issue. It is recommended that you provide as much details as possible around the issue to ensure it is understood by the developer.
    • Tasks
      • Tasks are very important as they measure the total completion of the issue so all changes you wish to apply to the files should be listed as tasks. Tasks are closed by the developer as they are fixed.
      • Users should be able to agree with the developer that the tasks are implemented correctly thus as a licensed user you are able to follow tasks completions which you will receive as notifications from the system.
      • You can add as many tasks as is required for the issue
    • Subscribers
      • Subscribers are people you think would benefit from being informed about the issue and the processing of the issue. Subscribers are always licensed users within the system and as such will receive notifications around the issue i.e. as the issue is migrated across the Kanban board, or tasks are completed or comments are raised.
    • Business Unit
      • All licensed users of the system belong to a business unit
      • Business units enable the administrators of the system to easily manage the resources available to perform work around issues.
      • When you select your business unit the user list in assignee field will filter based on the users assigned to the business units
      • This is a good way to find development users for your business unit
    • Assignee
      • Business unit will filter the assignee list to make it easier for you to find the relevant people you wish to assign the issue to.
      • Assignee is responsible for processing the issue
    • Priority
      • Low
        • The issue is not effecting the user experience of the file
        • Does not have any adverse effect on the environment
        • Does not affect the user’s interpretation of the data
      • Medium
        • The issue may be effecting user experience
        • May have adverse effect on the environment
        • May potentially affect the user’s interpretation of the data
      • High
        • The issue is effecting user experience
        • Is having an adverse effect on the environment
        • Is affecting the user’s interpretation of the data
      • Critical
        • File is not accessible
        • File is not working correctly
        • File is affecting the environment adversely in a way that would cause the environment to become unstable
      • Active
        • Leave the issue ticked should you wish the issue to remain active. Active issues are placed on the Kanban board for processing.
        • Tick the issue active box to inactive should you wish the issue to become inactive. Inactive issues are not visible on the Kanban board and will not be processed by admin and developers.
      • Save
        • Click the save button once you are satisfied with all the information you have provided around the issue.
        • Clicking the save button will process active issues to the Kanban board as well as into the issue list

Example of your issue under active issue list

  • Cancel
    • Clicking on the cancel button will cancel the issue request

Once you have saved your issue you can now add additional content to your issue such as link you issue to a file, or add attachments such as specification requirements or project plans.

  • Comments
    • The comments section will show all comments every added to the issue. You can add comments which will show on the issue and visible for the developer to review.
  • Files
    • You can add files to your issue.
    • Clicking on the file selection dropdown list will provide you with a list of all files, you can type into the dropdown list to search for your file in the list and make it easier to find the file in question.

  • Click on the Add button to add the file
  • You can only add one file at a time so perform this task multiple times should you wish to add additional files to the issue.
  • Attachments
    • You can add attachments to your issue. Attachments such as specification documentation, business plans, project plans, budget approvals and so forth are good supporting documentation for any issue and would ensure efficient processing of the issue.
  • Notifications
    • All notifications that have been sent around the issue will show here.
    • Notifications are sent when:
      • Issues are moved on the Kanban board and thus statuses have changed
      • Comments are added to the issue
      • Tasks on the issue are ticked off as completed
      • Issues are released to UAT
      • Issues are published to PRD

 

Once you save your issue all changes will be updated to the issue.

As a non-licensed user this is where your interaction with the issue on the system stops. You can communicate with the assigned developer via email for updates. Should you wish to track and monitor the implementation of your issue please contact your administrator for access to a user license.

Yes No

Dragging Issues on Kanban Board #

Our Kanban board enables you to drag and drop issues across the board and by doing so will affect the status of the issue or create a release of the issues or publish the issue linked file into a publication environment as set up by your administrators.

Please Note: Moving an issue across the board means that notifications will be sent to the reporter and interested parties identified on the issue.

Generally, publication environments support the development process as follows:

DEV

The DEV environment is the Development environment where all files should be checked-out to when you wish to develop them further. The development environment generally would be a development node or stream in Qlik Sense or a shared development folder in QlikView.

The development environment generally would not allow for business users to access it, but would purely be for developers to investigate, apply fixes and perform their own testing before they release a file to the business user for testing.

In the Kanban board this method of work is supported enabling the developer to move his issue and associated file across the board based on his development process. Issues can move either left or right across the board and dropping them into certain statuses on the board will change the status of the issue accordingly.

To Do Column

The To Do column provides two options when you drag your issue across the Kanban board. Dropping your issue into these highlighted areas called bands will change the status of the issue accordingly.

  • Open Band
    • Whenever a new issue is created it will be posted into the DEV stream with a status of Open.
  • Reopen Band
    • The reopen band change is used for issues that have been rejected or resolved before so that issues can be reopened subsequent to the decision being taken, and reopening the issue instead of creating a new issue means you can retain all historical changes and collaborations around the issue.

Done Column

The Done column provides three band options when you drag your issue across the Kanban board. Dropping your issue into these highlighted bands will change the status of the issue accordingly.

  • Rejected Band
    • The rejected band should be utilized for issues that have been rejected by either the developer, stakeholder and or business user.
  • Resolved Band
    • Resolved means that the issue has been resolved through a fix or it could not be replicated but the requestor has accepted that the issue can be resolved. Resolving the issue keeps the issue in the stream so you should deactivate the issue if you wish it to be removed from the board.
  • Create Release Band
    • Please Note: Business Users are not able to create a release
    • When you drop your issue into the Create Release band the WIP system will create a release of the issue and place it into the UAT stream with an Open status.
    • Creating a release is the only way to move your issue to the UAT stream, and that is as a release of the work that is now ready for testing by the user.

UAT

The User Acceptance Testing (UAT) stream functions under the same columns of the Kanban board and provides for three drop options within the Done column.

The user acceptance testing process is an iterative process between the developer and the user for testing the work that has been performed on the file. The developer will publish the file so that the testing user can access the file in the UAT/Test/Pre-PRD publication environment and will move the release across the UAT stream as the testing commences.

  • Rejected Band
    • The rejected band should be utilized for issues that have been rejected by either the developer, stakeholder and or business user.
  • Resolved Band
    • Resolved means that the issue has been resolved through a fix or it could not be replicated but the requestor has accepted that the issue can be resolved. Resolving the issue keeps the issue in the stream so you should deactivate the issue if you wish it to be removed from the board.
  • Publish
    • Please Note: Business Users are not able to publish applications
    • The publish band enables the developer to publish the release into the production (PRD) environment.
    • Dropping the release into Publish will bring up the publication view which enables the user to publish the file to an environment.

A release can be dragged across to the PRD environment

PRD

The Production (PRD) stream functions under the same columns of the Kanban board and provides for three drop options within the Done column.

  • Rejected Band
    • The rejected band should be utilized for issues that have been rejected by either the developer, stakeholder and or business user.
  • Resolved Band
    • Resolved means that the issue has been resolved through a fix or it could not be replicated but the requestor has accepted that the issue can be resolved. Resolving the issue keeps the issue in the stream so you should deactivate the issue if you wish it to be removed from the board.
  • Publish
    • Please Note: Business Users are not able to publish applications
    • The publish band enables the developer to publish the release into the production (PRD) environment.

Dropping the release into Publish will bring up the publication view which enables the user to publish the file to an environment.

 

Yes No

BOARDS: Dashboard #

The dashboard provides a complete view of the user’s activity across the system.

  • Business users can only see their own content
  • Developers can see their own content
  • Admin users can see all the content

The dashboard is broken up into four sections

  • Reported by me
    • These are all issues reported by the signed in user
  • Assigned to me
    • These are all the issues assigned to the signed in user
  • I Subscribe to
    • These are issues I have subscribed to as an interested party
  • Notifications
    • All notifications will reflect in this section
  • User Access Request (Admin Users Only)
    • This view presents a list of users that have requested access to the system
  • Pending Publications (Admin Users Only)
    • This view presents a list of users that have requested the admin user to publish applications / files for them. This would mean that the user either didn’t have the rights to publish to a certain environment or the user’s file does not meet the complexity threshold of a certain environment.
Yes No

MANAGE CONTENT: Files #

The files section is where you manage all your files, both in the WIP repository as well as access files via the Application Protocol Interface (API) integrated to your product-based files and repositories.

Yes No

WIP Repository Files #

You can access the WIP repository files from the hierarchical folder section as per the image provided.

You can browse your files in each folder and see them based on their checked-in/out status or you can search using the column based provided search fields.

All Files

Selecting the all files button will show all the files in the repository within the files list pane.

More

Clicking on the More button opens up the various options you have under the more option.

  • Create Root Folder
    • A Root folder is the highest-level folder you are able to create. You can create many levels of subfolder structures underneath a root folder.
  • Create Subfolder
    • Subfolders are created into a sub hierarchy of the existing folder you are in. To create a subfolder, click on the folder you wish to have as the subfolder’s parent folder, click on more and create subfolder. This will create a subfolder underneath the current folder you are currently accessing.
  • Edit Folder
    • Will enable you to edit the folder you have currently selected, so select a folder and click on the Edit Folder button to edit the folder. The edit folder option will enable you to change the folder name and assign different security groups to the folder level.

  • Creating a subfolder will require that you provide both a name and assign group level security to the folder you are creating.

  • Once you have saved your folder’s name you can assign group level rights to your folder by clicking on Security tab.
  • You can both add and remove groups from a folder by clicking the respective buttons and accepting the action.

 

 

  • Folder Security
    • You can access folder security by choosing Edit Folder from the menu list and choosing Security from the Properties section
    • WIP enables users to assign group security levels to folders. This will enable different groups to be able to interact on files within a folder in different ways
      • Read
        • Groups that have this assigned will be able to read (view) the files within the folder
      • Write
        • Groups that have this assigned will be able to edit and work with files within the folder such as check-in/out
      • Create
        • Groups with Create rights will be able to add files to the folder
      • Delete
        • Groups with Delete rights will be able to delete files within this folder
      • Publish
        • Groups with Publish rights will be able to publish files within this folder
      • ChPer (Change Permissions)
        • Groups with Change permissions rights will be able to change the permissions on the folder
      • Own (Change Owner)
        • Groups with Change Owner rights will be able to change the owner of the folder

 

 

  • PubProp (Publication Properties)
    • Groups with Publication Properties rights will be able to change the publication properties of the folder

  • Please see security section for assignment of group rights
  • You can assign, and affect security after the fact, group level security to a sub hierarchy by ticking the Reset permissions on all children and enable propagation. This means that changing the security after you have set it will propagate the changes to all the subfolders of the folder you are currently editing.
  • Edit Folder
    • Click on a folder and click on edit folder to edit the folder you are currently in. Editing the folder will enable you to change the folder name and group level security access to the folder.
  • Delete Folder
    • Click on a folder and click delete folder in order to delete a folder.
    • Please Note: Deleting a folder will also delete all the subfolders to that folder.

 

Yes No

Editing Files #

You can work with a file by clicking on the file and highlighting the file within the file list. Please note you can select multiple files at the same time (grey background) so should you wish to check out / in or publish multiple files you can click on multiples files and then select the action you wish to apply.

File Edit

  • Selecting a file and clicking on the Edit button will bring up the selected file’s properties view.

File Properties: Identification information & +Check-Out
  • The main window will provide the Identification information and check-out information about the file.
File Properties: Versions

Please note: The specific file version properties provides the same action buttons you have on a file level so every action you perform will be performed on that specific version of a file not master file that is managed in the WIP repository. See Edit File section for a description of the action buttons.

  • Edit
  • Delete
  • Get
  • Check In and Check-Out
  • Undo Check-Out
  • Publish
  • Compare
  • Cancel
  • The versions section of a file will provide you with all the historical version of the file within the WIP repository
  • Selecting a specific version of the file provides the Edit option
  • Clicking on the Edit option will open that specific version’s properties where the user can review the version properties and version content (see compare) of the specific version

Impact Analysis
  • The impact analysis provides a view of both the file impact analysis as well as the data lineage of the file
  • The Impact analysis view if dynamic so the user can click on the active (input/output) file to view where this file is being utilized and or an input / output for other files

  • As an example: Clicking on VM_DL03_DASHBOARD.qvf in the image below will take me to the impact analysis view of where this .qvf file gets it’s data and it’s data’s source view.
  • In this view we can now see that Sales orders.qvd is actually generated from sales orders.xls which loads the VM_DL01_QVDGEN.qvf which is a .qvd generator which then generates the sales orders.qvd file.

Publication History
  • Publication History of a file will show a view of every version of the file and where that version which environment that version was published into.
  • You can select the Environment you wish to view from the provided dropdown list of environments. Changing the environment from the dropdown list will show that file’s publication history for the selected environment.

  • You can select a file from the list and click on the Rollback button which will rollback the file to the previous version of the file that was published into that specific environment.
  • This feature is very handy should you publish a file into an environment and the file is not working anymore so some or other reason. You can rollback to the previous working version of the file while you fix the problem in the latest version.
  • In the image below you can see we have replaced version 1.0.9 of the file with version 1.0.8 of the file so the latest version of the file in the environment is 1.0.8

Destinations
  • The destinations of a file are the destination of the file you pre-set when a file is check-out or published to the selected environment. This will override the destination settings of the folder
  • This feature is very useful for administrators of environments to ensure that the files not exposed to areas they should not be in for governance and security reasons
  • The Destinations options enable the user to add multiple destinations per environment or edit existing destinations or delete destinations
  • You can rename the file when you publish to an environment, so that the file has a different name within the destination folder/stream you have selected

Variables
  • File level variables enable the user to assign variables to the file or link globally defined variables to the file, when a file is checked-out or published to an environment.
  • Variables are useful for instance if a user wishes a file language to change based on the environment they published the file into they can define the file language for that environment as a variable and when users access the file from that environment the default language will be the variable language. It can be also used to define functions, paths and connections in the scripts and in the application UI
  • Variables can be added by clicking on the Add variable
    • Provide a name and variable value for the variable
  • Variables can be linked by clicking on the Link button
    • Select the global variable you wish to assign to the file

Connections

  • Folder Connections are defined on a global or local file level
  • See Folder Connections section for a detailed description of Connections

  • You can create new connections by clicking on the Add Connections button

  • You can Link global folder connections to the file by selecting the Link button.

  • You can unlink global connections by selecting the connection and clicking the unlink button
Complexity Analysis
  • You can review the complexity analysis across different file versions within the complexity analysis view on a file level.
  • The complexity analysis provides you with a view of all the different categories that influence the complexity of a file and the score, percentage or value of the specific category for the file.
  • This view is useful to see when you are in the process of optimizing your application or you wish to see why an application suddenly does not perform well within an environment.

File Check-Out

  • Selecting a file and clicking the Check-Out button will automatically check-out the application or file to the destination defined for the file and add the check-out metadata to the version checked out

File Check-In

  • Selecting a file and clicking the Check-In button (should this file be checked-out) will bring up the file check-in form

  • The check in form requires that you add a Check-In Comment to the version you are checking-in. The comment allows other users to follow what changes you have applied to the version
  • Version Numbers are automatically assigned. You can change the major version number but the Minor and Revision numbers are automatically assigned to the version
  • Check-In But Keep Locked enables you to check in the file but keep it locked for editing by other users. This is generally used when you are in UAT process with a business/testing user and you don’t wish other developers to change the file while you are in testing phase
  • Empty Qlik Data is automatically ticked as some files could be very large and there is no benefit of bringing all the file data into the WIP repository unless you are weary of the source system and / or there is no time for a reload when the file has been published

Publish

  • Selecting one or multiple files and clicking on the Publish button will take you to the file publication form.
  • The default form will show you the File Name, publish comment, publication type, publication environment and reload automatically options.

  • Publish Comment
    • The publish comment is a required field and adds information to the publication for other users to better understand what has changed in the file published from the previous file published.
  • Publication Type

  • The publication type provides two options for publishing your file, Should you have the rights to publish you will be presented with this options
    • Immediate: Publishes the file to the selected environment(s) immediately
    • ForApproval: Does not publish the file but sends a request to the administrator users to publish the file. Note that is you have only “publish for approval” right on one of the selected environments then you will only be able to publish for approval, not immediately.
  • Select Publication Environment

  • Clicking on the select publication environment will bring up all the possible environments the user is able to publish into.
  • You can select one or multiple environments to publish into at the same time
  • Selecting an environment will bring up the environment checklist as well as the complexity analysis view for the environment
    • Environment Checklist: The environment checklist if defined per environment and has optional and required checks per environment that should be fulfilled and checked by the developer/publisher or they will not be able to publish the application into that environment
    • Selecting multiple environments will bring up the checklists for all selected environments

  • Environment Complexity: of the file compared to the index threshold set for that environment and will return a pass or fail view per environment selected. This will help the user identify whether his file will be allowed to be published into the environment or not.

  • Should you have a file that fails the environment complexity analysis threshold you can click on the Fail message to review the reason your file has failed i.e. in the example image below the Cardinality of the data threshold is to high for the 02-QSENSE-223-PRD environment

  • Should you have a file that fails the environment complexity analysis threshold WIP will enquire whether you wish to request dispensation from the Administrator users in order to publish the file. This means that the request will go to Admin users and they will be able to publish the file should they approve the publication of the file to the specific environment.

  • Should you meet all the publication requirements your file will now be published into the environment(s) selected and can be automatically reloaded once published into the environment.

File Publications

  • Selecting a file and clicking the publish button will bring up the publications view for that specific file
  • The publications view of the file will show you the latest version of the file across all environments as well as who published it and what the publication path for the file within that environment is i.e. which stream or folder it is published to in that environment.
  • The publications view also provides a button that will take you to the Rollback view in the publication history of the file, should you wish to rollback the file within a certain environment.

File Destination

  • The destinations view provides a view of the various destinations set of the file when it is checked out or published across the different environments.

File More: Properties

  • Clicking on the file properties button will bring up the standard file properties view and alternative Version Content view.

  • The Version Content view provides you with a hierarchical structure view and values of all the metadata about your file. You can expand all or collapse all be clicking on the buttons provided.

File More: Compare

  • Selecting multiple versions will provide the Compare option which will enable the user to compare two versions of the same file to one another
  • There are two ways to compare your files
    • Selecting the Compare function from the file level will automatically compare the latest version of the file with the previous version of the file. The comparison will provide you with a hierarchical view of the structure and value of the previous version of the file on the left and the comparative view of the latest version on the right and will compare all changes on every line of metadata
    • Editing a file and going to the versions section of the file and then selecting two different versions of the file will provide you with a comparison of two specifically selected version of the file

  • Selecting the Only Difference option will show you only the differences of changes between the applications
  • Change Colour Codes:
    • Red: Red means that something has been deleted from the previous version of the file
    • Blue: Blue means that something has changed from the previous version of the file
    • Green: Green means that something has been added to the latest comparable version of the file vs. the previous version being reviewed

File More: Delete

  • Selecting a version and clicking the delete button will delete that file or file version from the repository

File More: Get

  • Selecting a version clicking the Get button will Get a copy of the file but not check the file out of the repository

File More: Undo Check-Out

  • You can undo a checkout should you wish to ignore any changes made to the file within the checked-out stream/folder.

 

Yes No

Accessing Product Files #

You can access the files within your product repository or file structures by browsing the product Application Protocol Interface (API) access button.

Here is an example of the Qlik Sense API button

Here is an example of the QlikView API access button

The API access will change based on the product you have logged into i.e. logging into Qlik Sense and a Qlik Sense workspace will give you the Qlik Sense API access option.

By clicking the API access button, you can browse the related folder/stream based files

Please Note: The product icon you used to access the API will turn grey with a x cross on it. You can click on this icon to close the API browsing window.

Import Files

Drag/Drop

You can browse your product files and drag/drop them into the WIP repository folder of your choice.  Performing this action will automatically check the file into the WIP repository.

Check-In File

While you have the API list of files open, click on the WIP repository folder you wish your file to be checked into, click on the Check-In button.

Note: Drag/Drop can add only one file at a time when Check-In can add multiple ones

Yes No

MANAGE CONTENT: Content Libraries #

The content libraries are integrated to the Qlik Sense API and will connect to the Qlik Sense Content libraries stream. Content library files can be managed in the same way as all other files are managed through check-in/out and publication processes.

To browse your Qlik server click on the QlikView / Qlik Sense Icons or access other files through by clicking on the Import File icon.

 

Yes No

MANAGE CONTENT: Folder Connections #

You have two types of connections in Qlik.

Connections insure that your connections to your various data sources always work within the environment you are publishing your applications into. WIP will automatically update the connection based on the environment published.

  • Data Connections
    • Data connections are set up on an application level and can be various types of connections. Data connections are set up on an application level so you can connect to many different data stores and data types via your application.
    • WIP also manages your data connections on the file level thus you can access your file data connections from the file properties.
    • Additionally, to file level connections you can also set up global connections that will be accessible for all files.
    • To browse your Qlik server click on the QlikView / Qlik Sense Icons or access other files through by clicking on the Import File icon.
  • Folder Connections
    • Folder connections are utilized for your “LIB” folder connection content. You can manage the files in your folder library connection within WIP and any updates on the files will then be migrated to your server as published from time to time.
    • Folder connections are integrated to your Qlik Connections via the API. When you connect to your Qlik server it will automatically display all your content in your Qlik Connections via the API connection to your Qlik Server. You can now drag/drop your various connections, includes, files etc. into the WIP repository folder of choice.
    • To browse your Qlik server click on the QlikView / Qlik Sense Icons or access other files through by clicking on the Import File icon.

Yes No

MANAGE CONTENT: Extensions #

Qlik supports many different types of extensions. Extensions can be several different things: A widget library, a custom theme, or a visualization extension to visualized data such as an interactive map.

WIP integrates to your Qlik server and accesses your extension libraries. You can drag/drop extensions into the WIP repository and manage them accordingly. WIP will manage your extensions in the same way that it manages a file.

To browse your Qlik server click on the QlikView / Qlik Sense Icons or access other files through by clicking on the Import File icon.

Yes No

MANAGE RESOURCES: Issues #

The issues list provides a list of all active issues by default. Active issues are still work in progress thus visible on the Kanban board. Deactivating an issue will remove it from both the Kanban board as well as the active issue list.

You are able to filter the issues based on the following criteria:

  • My Issues
    • My Issues will reflect all issues which you have been assigned to as assignee
  • Reported By Me
    • Reported By Me will reflect all issues that you have reported
  • Subscribed To
    • Subscribed To will reflect all issues that you are subscribed to as an interested party
  • Recently Updated
    • Will reflect all the recently updated issues within the last month

Ticking the Active Issues box will show you all the deactivated issues. These are issues that have been completed and should not reflect on the Kanban anymore. The filter will still apply on the deactivated issues list.

Yes No

WIP Repository Add Files #

If you have not added any files or wish to add some additional files to your issues you are able to browse the WIP repository folder, stream, connections, content libraries and so forth.

You can browse the files by clicking on the WIP product logo as indicated in the image, and drag/drop the files into the issue or release you wish them to be added to. Linking files to issues ensure they are published accordingly when you are ready for publication.

Yes No

MANAGE RESOURCES: Publication History #

The publication history section enables you to search for publications based on a date range which can be set by selecting the From Date and To Date calendar sections and selecting the date range. Additionally you can search your publication history by creation date, publish by, publication type, publication status, description, publication date, and based on the type command line used.

Selecting a publication will show the environment, files, published version, previous version, publication status, publication folder path, publication errors for that specific publication.

Selecting the publication will enable you to rollback the publication or a specific of a file version within the publication

Clicking on the Rollback Publication button will rollback the total publication to the previous version of all the files within the publication.

Clicking on the Rollback Version button will rollback the file you have selected to the previous version of that file within the published environment.

Yes No

MANAGE RESOURCES: Global Standards #

Global Variables and Global Connections can be linked to any Qlik application in your WIP repository. Common variables and connections used by your applications should be created here, as a central global standards library, for quick access from any files.

 

WIP enables you to create different variables and connections where the default value will be the same but different values will exist based on the environment you publish your standards into. You will thus have a central place where you can manage all your global standards.

 

To automatically change the value of a Variable or Connection when publishing to an environment, first select the Environments filter on the right. Note the Default Value will be replicated in the Environment Value no matter which environment you select. You need to edit the Environment Value with the Environments filter applied. Your global standards variables and connections values will automatically be applied when linked to a file.

  • To add a variable, click on the “Add Variable” button.
    • You will be asked to provide a variable name and the default value for the variable – To save the variable click “Save”

  • To add a Connection, click on the “Add Connection” button
    • You will be asked to provide a Connection name and the default value for the Connection – To save the Connection click “Save”

Yes No

CONFIGURATION: Servers #

Admin users are able to create, edit and delete servers from the WIP repository. Server setup are where the admin users will configure the setup and connection to the QlikView and Qlik Sense servers. If you are logged into Qlik Sense you will attain all the Qlik Sense configuration options and vice versa for QlikView and SAP Analytics.

Please review the Administration Guide for a detailed view on server configurations.

Yes No

Environment List #

You are able to access a specific environment from the servers option and by double clicking on a specific server and selecting the Environment List option from the server Properties window.

Double clicking on an environment will open the Environment edit Properties

In the environment edit properties view you can change the name and description of the environment and define whether Login is enabled for the environment. You can also define whether the specific environment is a Production Environment by checking the provided box.

Yes No

Security #

The environment security options enable you to add groups to the environment that are able to perform different functions on the environment as defined within the group specific configuration.

Clicking on Add Group will provide you with an available list of groups that can be added to the specific environment. Select the group and save your selection.

Assign Environment specific rights to a group by clicking on the provided Permissions options

  • Read: Groups with this right enabled can read content within an environment
  • Publish: Groups with this permission can publish into the specific environment selected
  • Publish For Approval: Groups with this right enabled will have the Publish For Approval workflow enabled for this environment
  • Change Permissions: Groups with this enabled will be able to change
  • Publication Properties

Reset Permissions On All Childrens And Enable Propagation

Yes No

Check-List #

Check-Lists are configured per environment.

The Admin users can Add Tasks by filling a task name and clicking on the Add Task button.

The administrator users can add optional and required tasks that should be checked as validations that the users have conformed to such required tasks before they are able to publish into the environment.

Once the field has been created the user can then edit the field, or assign the field as a required field or delete the field from the provided action items.

Yes No

Complexity Analyzer #

The complexity Analyzer thresholds setup per environment enables you to set up the complexity per environment. You can drag the various categories measured as part of the complexity index (See Complexity Analysis Index) to set the thresholds you wish to apply to the specific environment.

When you set the complexity thresholds on an environment any file that does not pass all complexity category thresholds will not be allowed to be published into the environment and would require the user to request dispensation from the administrators, who can then publish the file.

Yes No

CONFIGURATION: Users #

User Validation Required #

When users request access to the system they will require validation from the admin user as assigning a user to the system requires a license.

Admin users will receive a notification on their dashboards.

Clicking on the user will take the admin to the edit user properties where user rights can be assigned to the user.

Alternatively, the admin user can go directly to CONFIGURATION – Users, and check the “Validation Required” box which will display all users waiting for validation.

The admin user can now assign user rights to the user which will enable the user account access various system functions and assign the user to user groups.

Yes No

Assigning User Rights #

High level user rights are assigned on a user level. It is possible to assign rights to users on the following levels:

  • QlikView
    • Assigning this right by clicking the checkbox will enable the user to access the QlikView files within the repository (Read, Write, Delete)
  • Qlik Sense
    • Assigning this right by clicking the checkbox will enable the user to access the Qlik Sense files within the repository (Read, Write, Delete)
  • User Portal
    • Assigning this right by clicking the checkbox will enable the user to access the User Portal as a business user or analyst. These rights should be applied to users that wish to access and review their own issues on the Kanban board, and interact through collaboration and notification around their issues.
    • Activating this for the user will also provide the user access to their own dashboard where they can track all interactions across all their issues.
  • Files
    • Assigning this right by clicking the checkbox will enable the user to access all files within the repository (Read, Write, Delete)
  • Publication Properties
    • Assigning this right by clicking the checkbox will enable the user to access and manage publication properties of the files
  • Enable Publication
    • Assigning this right by clicking the checkbox will enable the user to publish applications to the assigned environments where the user has been granted access through their respective groups

Please Note: Assigning rights to a user will consume a user license based on the rights assigned.

Yes No

Avatar #

The admin user can also assign an avatar to the user.

  • User can change the avatar or load their own image into the system once access is assigned to the user. Select from default avatars
  • Users can import their own avatars and images by clicking SELECT TO IMPORT, this will open your file browser where you can browse to the file you wish to import. You will be requested to crop the image to the supported size. Click on Save when done. The image will now display as your current avatar.
  • Users can drag/drop files into the DRAG AND DROP HERE section. You will be requested to crop the image to the supported size. Click on Save when done. The image will now display as your current avatar.
Yes No

CONFIGURATION: Groups #

Groups are an important configuration for WIP. It is recommended that you always use groups to assign rights to users, meaning that even if you have one user with specific rights that no other user or group of users have, you should still assign that user to a specific group.

Please Note: WIP will automatically create an Administrator group when it is installed

  • Create
    • You can create new user groups by clicking on the + Create button
    • You are requested to provide a Name and Description for the group
    • Please Note:
      • You can assign this group as an administrator group which will enable anybody from the group to access the administration features of WIP.
    • You should provide a name and description and save the group before you are able to assign users to the group
    • You will receive a list of all the licensed users in the system as Available Users, and you can either click on the “Add All” button, or you can drag users into the Allocated Users area, and drop the user to add the user to the Allocated Users area.

  • Edit
    • Clicking on the Edit button will open the selected group for editing. Editing enables you to change any information about the group such as the name, description and allocated users to the group.
  • Delete
    • Clicking on the Delete button will delete any selected groups. There will be a validation requirement pop up that will require you to confirm you wish to delete the selected group(s).
    • Once you have clicked on the Yes option, the group will be deleted from the repository
    • Please Note:
      • Deleted groups will be permanently deleted from the system and would need to be recreated should you wish the group to exist again.

 

Yes No

CONFIGURATION: Active Directory #

The Active Directory integration configuration option enables the administrator users to define domains and get the domain users and groups automatically synchronized into the WIP user management system.

Alternatively, should you not have an Active Directory server you can import your users by clicking on the Import Users button

 

Yes No

CONFIGURATION: Business Units #

Business Units are an important configuration for WIP. WIP will automatically filter any users lists based on the business unit(s) the users have been assigned to, within the user’s configuration. This configuration makes it easy for users to find their own people within the system.

Please Note:

There will always be a default business unit. You can either use this business unit or change the name of the business unit.

  • Create
    • You can create new business user by clicking on the + Create button
    • You are requested to provide a Name for the business unit
  • Edit
    • You can edit existing business units by clicking on the edit button.
  • Delete
    • You can delete existing business units by selecting the business unit(s) in question and clicking on the delete button. This will require a confirmation for deleting the business unit(s) selected.
Yes No

CONFIGURATION: Options #

The Options section is where your system wide configuration options are configured. Changing these options will apply changes throughout the system accordingly.

  • Scan Level
    • The scan level is the level you wish to scan the applications and files when they are checked into the repository.
      • 1 (recommended)
      • 2
      • 3
    • All three scan options will scan all the available options on a file but will provide a more detailed content of the file for comparisons and version content.
    • Please Note: Changing the scan level to a deeper level 1-3 will require more time to check you files into and out of the repository
  • Allow duplicate file names
    • When you enable this through clicking the check box, you are allowing users to check-in files with exactly the same name. This will mean that instead of WIP managing one master file it will start to manage multiple master files when the file name is the same as the one already in the repository.
    • Please Note: Ensure you have a very strict version management structure and policies in place before enabling this on the WIP platform.
    • Please Note: This option can’t be reverted It’s one way
  • Tag Files
    • When you enable tag files to the system by clicking on the checkbox it will enable WIP to add the WIP version to the file when checked out / published to the environment
  • Add WIP Version To File Commentary
    • SAP-Analytics add the WIP version the file commentary
  • Disable Check-In when File is Checked-Out
    • Prevent a user from checking in a file if another user has checked out the same file. This forces one of the users to undo checkout
  • Enable Check-In Only If File Is Checked-Out
    • Prevent adding files by drag & drop if the file already exists and is not checked out
  • -Enable Check-In Of Previous Versions
    • Allow the check-in on a version number lower that latest version
    • Please Note: Ensure you have a very strict version management structure and policies in place before enabling this on the WIP platform.
Yes No

License #

The WIP license section enables the administrator user to paste the license code into the license area defined and to save the code. Once saved the license code will unlock the license amounts as have been defined by the code provided to the system.

The license code will unlock the Product options and number of licenses per product option. The administrator user can come to the license section to review how many of which product option has been assigned to users throughout the system. The license will also reflect the expiry date of the license. This will inform the administrator user as to when the license should be renewed.

Yes No

Kanban #

The Kanban configuration options enables the administrator to configure the Kanban board. The administrator can activate various options on the Kanban board according to the available check boxes within the activate columns. Activating these options will display these options on the Kanban board and deactivating them will remove them from the Kanban board this should you not have a To Do area on your current Kanban just deactivate the To Do option by clicking on the checkbox.

The Kanban status options “Column” column options will place the options within the columns as defined per status option i.e. when dragging your issues, you will find the status options within the defined columns in your Kanban

Yes No

Email #

The email configuration is where you will configure the Simple Mail Transfer Protocol (SMTP) of your WIP server. This will require that you have the necessary configuration information of your company SMTP server and have created a user for WIP to be able to send notifications from the system via email.

  • SMTP Server
    • This is generally your company SMTP server and generally will take the format of smtp.yourservername.yourserverdomain example : smtp.google.com
  • SMTP Port
    • The SMTP port should be assigned as assigned to you SMTP configuration meaning this will allow WIP to access your SMTP server through the defined port. Ports number depend if the SSL option is active or not, can be 465, 587 or 80
  • Username
    • The username is generally an email address that has been created for the WIP service and will be utilized to communicate with the WIP users. This would generally be wip@yourservername.yourserverdomain
  • Password
    • The password should match the password you have defined for the username on your SMTP server
  • From Mail Address
  • Enable SSL
    • Ticking this box will enable Secure Socket Layer (SSL) security on the SMTP connection so if you have enabled SSL security on the SMTP server then you will be required to activate this within the WIP service.
  • Validate SMTP
    • You can test your SMTP setup by clicking on the validate smtp button. The system will test the configuration and should there not be any errors in the testing it will return a Success comment.
      • SMTP Server – Object reference not set to an instance of an object
      • SMTP Port – A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied
      • Username – shows success even when its incorrect, needs to give an error
      • From mail address – shows success even when its incorrect, needs to give an error

Yes No

Complexity Analyzer Index #

Each Qlik Application has a Complexity Index value in the file. The complexity value of a file is a sum of several different measures of complexity of a file’s content, including number of tables, number of fields, number of sheets, objects, expressions, calculated dimensions, etc. WIP users have the option of changing the weighting factor for any of these individual complexity measures as well as setting their thresholds.

 

Applications that exceed the threshold of one or more attributes are probably those whose performance could be improved by reducing their complexity. Their improvement is also likely to benefit the QlikView Server performance by reducing system resource requirements.

 

The measures in the Complexity Indexes are:

  • Base is the level for factoring into the complexity index. If a file contains tables, sheets, or other objects whose counts are below the base settings, then those elements are not calculated in the complexity index. Any number that exceeds the base is used in the complexity index. For example, if the Tables Base is 5, and a file has 6 tables, then 1 would be used to calculate the complexity index.
  • The Max value is used as a divisor in the complexity index calculation, so the higher the Max value, the lower the impact of counts that exceed the Base.
  • The Weight is a multiplier in the complexity index calculation, so the higher the Weight, the greater impact of counts that exceed the Base.
Yes No

WIP Release Notes and Roadmap #

Release Notes and Roadmap

Introduction

This document contains a list of the changes and enhancements that was made to WIP in the different version releases. It will also contain a list of issues that has been fixed in each version.

For a more comprehensive list of known issues, please either register on the ebiexperts website (www.ebiexperts.com/register-2) and see the Knowledge Base (click on ‘Help’) section under your profile or refer to the document ‘Restrictions & History’.

Upcoming future enhancements

  1. WIP for SAPAnalytics
  2. Scheduled reload tasks
  3. Recursive folder hierarchy check in
  4. Global search
  5. Client addon to open client QlikView application
  6. WIP publish workflow
  7. WIP layout customization
  8. WIP for NPrinting
  9. Qlik Sense WIP extension

Release Notes

WIP January 2018

Enhancements

  1. Complexity Analysis for Qlik Sense and QlikView
  2. Request dispensation to publish an app overriding complexity
  3. Publish for approval
  4. Users approval
  5. Active directory user’s import
  6. Qlik Sense user’s directory import
  7. Qlik Sense Governance App
  8. Fastest QlikView and Qlik Sense applications scan

 

WIP September 2017

Re-engineering

  1. WIP for QlikView
  2. WIP for Qlik Sense
  3. Full Web Angular UI
  4. KANBAN Style Agile Issues Management
  5. User’s dashboard
  6. Collaborative issues messaging
  7. User portal access
  8. Request user access
  9. Complete REST API
  10. Graphical Compare
  11. Graphical Impact Analysis
  12. Qlik Sense Content Separation
    1. Applications
    2. Content Libraries
    3. Folder Connections
    4. Extensions
  13. Business Units
Yes No
Oops! You need to be logged in to use this form.

Please identify yourself via e-mail