Environment Variable Extract
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
18-10-19 03:47 PM
------------------------------
Harshil Mehta
Solution Designer
Deloitte
America/Toronto
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
18-10-19 04:27 PM
At the end it should give you full extract in text file. You may play around with the Destination file format to get extract in right format.
PS: You can also use this data import export tool to change the data. Be very careful though. The only other way to change data is through SQL Server.
Appreciate any other suggestion. Thanks 🙂
------------------------------
Harshil Mehta
Solution Developer
Deloitte
America/Toronto
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-11-19 10:19 PM
I would suggest if you are using more than 5 global/environment variables then try to make a one simple config / excel file and maintain there itself.
and it is easy to maintain, edit, and also no one can touch/or change them because you can save that file in some particular location for the process where you have your other folder structure like inputs, outputs etc.
In the beginning of process, only you have to read the file and create global data items and initialize it.
I this case you have to create only one environment variable for config file path.
This is only the alternate approach and suggestion.
------------------------------
Mahesh Kushare
Sr. Consultant
Capgemini Solutions Canada Inc
Toronto
2269886490
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-11-19 10:35 PM
Thank you for sharing the suggestion. This is a good idea, but it is like adding an additional dependency. Also, it becomes very tricky when we work in multi developer environment. For now, we will have to just stick with extraction from database directly. We will think about using excel for future engagements.
Once again thank you for sharing the suggestion. Appreciate it!
Regards,
------------------------------
Harshil Mehta
Solution Developer
Deloitte
America/Toronto
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-11-19 06:11 PM
Was curious what is the need to maintain environment variables separately like this. You can have a deployment guide which will list this for a process. Also pulling this one time from DB is fine if you want to compare this in various environments.
------------------------------
Manas Jena
Sr Analyst
ZimmerBiomet
America/New_York
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-11-19 06:30 PM
------------------------------
Harshil Mehta
Solution Designer
Deloitte
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-11-19 06:43 PM
I think the good approach would be to maintain a separate document. Will will be Operations and Support. That can have a section say "Process Implementation Plan" .
This can have before during and post Implementation details.
SDD is more about high level solution details . Many organizations restrict direct DB access for consultants working on RPA projects.
------------------------------
Manas Jena
Sr Analyst
ZimmerBiomet
America/New_York
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-11-19 09:07 AM
------------------------------
Johny Jain
IT Solution Engineer
Kimberly Clark
Asia/Kolkata
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-11-19 02:35 PM
Hi,
do not know about the Release Map - might be a very good solution. Will check for myself.
if only Env Variables are in question - there is another way using simple powershell script from release file if that is working for you
1. you need to have a release file with required env variables
2. save the code below to GetEnvVarsFromBPRelease.ps1
3. edit $BPReleaseFile, $BPEnvVarsFile variables, change csv delimiter as you please
4. run the script on it to get CSV (might be redone to other outputs easily):
code between ###:
#############################################################
# change input bprelease path and filename and output file
$BPReleaseFile = "c:\temp\env.bprelease"
$BPEnvVarsFile = "c:\temp\BP_ENV_var.csv"
[xml]$xml_doc = Get-Content $BPReleaseFile -Encoding utf8
$xml_doc.release.contents.'environment-variable' | Select-Object -Property "Name","Type","Value" | ConvertTo-Csv -Delimiter ";" | Out-File $BPEnvVarsFile -Encoding utf8
#############################################################
------------------------------
Mindaugas Breskus
Software engineer
Swedbank
Europe/Vilnius
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-11-19 06:14 PM
Thanks,
------------------------------
Harshil Mehta
Solution Designer
Deloitte
------------------------------
