Downloads:
13,448
Downloads of v 2017.2.3.501:
397
Last Update:
01 May 2017
Package Maintainer(s):
Software Author(s):
- Pragmatic Works Software
Tags:
admin bixpress dbaxpress docxpress documentation excel hive inspect licensed lineage monitoring oracle pragmaticworks salesforce sharepoint sql ssas ssis ssrs surf trialWorkbench Server
This is not the latest version of Workbench Server available.
- 1
- 2
- 3
2017.2.3.501 | Updated: 01 May 2017
Downloads:
13,448
Downloads of v 2017.2.3.501:
397
Maintainer(s):
Software Author(s):
- Pragmatic Works Software
Workbench Server 2017.2.3.501
This is not the latest version of Workbench Server available.
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Pragmatic Works Software. The inclusion of Pragmatic Works Software trademark(s), if any, upon this webpage is solely to identify Pragmatic Works Software goods or services and not for commercial purposes.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Workbench Server, run the following command from the command line or from PowerShell:
To upgrade Workbench Server, run the following command from the command line or from PowerShell:
To uninstall Workbench Server, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download pragmaticworksworkbenchserver --internalize --version=2017.2.3.501 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade pragmaticworksworkbenchserver -y --source="'INTERNAL REPO URL'" --version="'2017.2.3.501'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade pragmaticworksworkbenchserver -y --source="'INTERNAL REPO URL'" --version="'2017.2.3.501'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install pragmaticworksworkbenchserver
win_chocolatey:
name: pragmaticworksworkbenchserver
version: '2017.2.3.501'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'pragmaticworksworkbenchserver' do
action :install
source 'INTERNAL REPO URL'
version '2017.2.3.501'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller pragmaticworksworkbenchserver
{
Name = "pragmaticworksworkbenchserver"
Version = "2017.2.3.501"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'pragmaticworksworkbenchserver':
ensure => '2017.2.3.501',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...
This package was approved as a trusted package on 07 Jun 2017.
Workbench Server
BI xPress Server, DOC xPress Server, and LegiTest Server are all included in this package, our three powerhouse team focused products. All of the included products come with a 14-day full featured trial or enter your product key for total access (separate download is not needed).
BI xPress Server
BI xPress Server allows your team to apply the Auditing Framework using unified settings and to monitor your SSIS packages in your web browser and on your mobile device. See more about BI xPress Server at https://www.pragmaticworks.com/Products/Bi-xPress.
DOC xPress Server
DOC xPress Server brings the metadata capabilities to a web browser, making it much easier to share documentation, lineage, and data dictionary information with your team. Generate documentation (PDF, CHM, and web pages) for SQL Server, SSAS, SSIS, SSRS, Excel, Oracle, Hive and much more with DOC xPress Server. See more about DOC xPress Server at https://www.pragmaticworks.com/Products/Doc-xPress.
LegiTest Server
LegiTest Server shows your team the health of your data-centric testing over time. View the test run results in a web browser and take action if a test doesn't pass. Your team can also re-run the test(s) from within a web browser to verify results. A test suite can also be run on a schedule so you know your data-centric applications are tested constantly. See more about LegiTest Server at https://www.pragmaticworks.com/Products/LegiTest.
$ErrorActionPreference = 'Stop';
$packageName = 'pragmaticworksworkbenchserver'
$softwareName = 'Workbench Server*'
$installerType = 'EXE'
$silentArgs = '/qn /norestart'
$validExitCodes = @(0, 3010, 1605, 1614, 1641)
$uninstalled = $false
$local_key = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'
$key = Get-ItemProperty -Path @($machine_key6432,$machine_key, $local_key) `
-ErrorAction SilentlyContinue `
| ? { $_.DisplayName -like "$softwareName" }
if ($key.Count -eq 1) {
$key | % {
$file = "$($_.UninstallString)"
if ($installerType -eq 'MSI') {
$silentArgs = "$($_.PSChildName) $silentArgs"
$file = ''
}
Uninstall-ChocolateyPackage -PackageName $packageName `
-FileType $installerType `
-SilentArgs "$silentArgs" `
-ValidExitCodes $validExitCodes `
-File "$file"
}
} elseif ($key.Count -eq 0) {
Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
Write-Warning "$key.Count matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "- $_.DisplayName"}
}
Log in or click on link to see number of positives.
- pragmaticworksworkbenchserver.2017.2.3.501.nupkg (9be7aa8a9176) - ## / 58
- Workbench_Server_2017.2.3.501.exe (7fed1abe7e2b) - ## / 61
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
Workbench Server 2018.2.4.504 | 754 | Wednesday, June 27, 2018 | Approved | |
Workbench Server 2018.2.4.503 | 316 | Thursday, May 3, 2018 | Approved | |
Workbench Server 2018.2.3.412-beta | 288 | Thursday, April 12, 2018 | Exempted | |
Workbench Server 2018.2.2.302-beta | 439 | Friday, March 2, 2018 | Exempted | |
Workbench Server 2018.1.5.312 | 345 | Monday, March 12, 2018 | Approved | |
Workbench Server 2018.1.4.208 | 355 | Friday, February 9, 2018 | Approved | |
Workbench Server 2018.1.4.129-beta | 334 | Monday, January 29, 2018 | Exempted | |
Workbench Server 2018.1.3.122-beta | 361 | Monday, January 22, 2018 | Exempted | |
Workbench Server 2018.1.2.1206-beta | 386 | Wednesday, December 6, 2017 | Approved | |
Workbench Server 2018.1.1.1030-beta | 353 | Monday, October 30, 2017 | Approved | |
Workbench Server 2017.4.7.1127 | 341 | Tuesday, November 28, 2017 | Approved | |
Workbench Server 2017.4.6.1107 | 334 | Tuesday, November 7, 2017 | Approved | |
Workbench Server 2017.4.5.1106 | 344 | Monday, November 6, 2017 | Approved | |
Workbench Server 2017.4.5.1018-beta | 369 | Wednesday, October 18, 2017 | Exempted | |
Workbench Server 2017.4.3.1010-beta | 380 | Tuesday, October 10, 2017 | Approved | |
Workbench Server 2017.3.3.807 | 386 | Monday, August 7, 2017 | Approved | |
Workbench Server 2017.3.3.710-beta | 391 | Monday, July 10, 2017 | Approved | |
Workbench Server 2017.3.2.605-beta | 410 | Monday, June 5, 2017 | Approved | |
Workbench Server 2017.3.1.502-beta | 416 | Tuesday, May 2, 2017 | Approved | |
Workbench Server 2017.2.3.501 | 397 | Monday, May 1, 2017 | Approved | |
Workbench Server 2017.2.3.330-beta | 392 | Thursday, March 30, 2017 | Approved | |
Workbench Server 2017.1.6 | 385 | Friday, March 3, 2017 | Approved | |
Workbench Server 2017.1.5 | 427 | Thursday, February 9, 2017 | Approved | |
Workbench Server 2017.1.4 | 443 | Thursday, February 2, 2017 | Approved | |
Workbench Server 2017.1.3 | 434 | Thursday, January 12, 2017 | Approved | |
Workbench Server 2017.1.2-beta | 434 | Tuesday, November 29, 2016 | Approved | |
Workbench Server 2016.4.5 | 423 | Thursday, November 3, 2016 | Approved | |
Workbench Server 2016.4.4 | 441 | Tuesday, November 1, 2016 | Approved | |
Workbench Server 2016.3.1-beta1 | 382 | Monday, May 2, 2016 | Exempted | |
Workbench Server 2016.1.5-beta5 | 414 | Tuesday, January 19, 2016 | Exempted | |
Workbench Server 2016.1.3-beta4 | 408 | Monday, January 11, 2016 | Exempted | |
Workbench Server 2016.1.3-beta3 | 490 | Thursday, January 7, 2016 | Exempted | |
Workbench Server 2016.1.2-beta2 | 412 | Monday, November 30, 2015 | Exempted |
© 2016
BI xPress Server version 2017.2.3.501
Updated Features
11047: Help Documentation for Notification Engine now includes details for configuring custom parameters
LegiTest Server version 2017.2.3.501
New Features
6809: Added ability to suppress test failures for a set time frame
9870: Tests can now be moved to trash, then deleted from the server.
- Tests can now be moved to trash from the summary page.
- Trash view has been added, this allows users to permanently delete tests from the server.
- Unexecuted assemblies can no be deleted from the server on the unexecuted assembly view on the summary page.
9871: Summary Page now has separate views for Run and Not run assemblies.
10272: Users can now select existing tags from drop down when tagging a test object.
10331: Test management page now shows an item's most recent status in the navigation menu
10911: Design system for handling authorization for cloud services
11046: Notification Engine now has dynamic html template for LegiTest status
Updated Features
6740: The "Export to Excel" feature within Grid Comparison now provides more details
- The file name for the excel spreadsheet now includes the date and time the test was executed
- The excel spreadsheet now contains a header that includes the suite, group, test and action name as well as the start and end time for the execution
9868: Test Scheduler page has now been simplified for ease of use
9873: Added "Missing Test Runner" topic to FAQ for LegiTest Server
Fixes
9169: "Already added" warning appears when adding a new item to a Coverage Report
9228: Spaces in an assembly name are causing them not to run from the server
9241: Deleting a test execution fails
9817: Side by Side table view for errors does not have consistent height on both sides
9821: Breadcrumb located on View Details Page does not link
9869: Tests not part of previous run are not represented as such.
10273: Parameters containing certain special characters are not displaying properly on the test management page
10330: Long names in management navigation menu extend past frame.
11021: Managing a test with an existing Hyperlink template, will not load the template area for editing.
11026: When viewing a grid comparison result on the server, rows with no information still show a hyperlink.
Workbench Server version 2017.2.3.501
Updated Features
10978: Help documentation for setup instructions now includes details for multi-domain considerations
Fixes
10346: Some operations within DOC xPress and System Dashboard aren't responsive or appear disabled
10382: Workbench Server does not populate Action and RoleAction tables in host database
This package has no dependencies.
Ground Rules:
- This discussion is only about Workbench Server and the Workbench Server package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Workbench Server, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.