V4 Editor and Variable passing

PowerShell Universal Universal Automation
1 
Product: PowerShell Universal
Version: 4.0.1

I recently updated upgraded to 4.0.1 and noticed two things, one may be a change in behavior but the editor is odd. When I open a script I am not seeing the entire script, stops at line 254, but if I view it in the configurations I see all 257 lines.

The other is when I launch a scheduled script from another script and pass some, data, in 3.x it came across as the data but now I get this when I view the job parameters:

<Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04">_x000D__x000A_ <S>mycustomdata</S>_x000D__x000A_</Objs>

Again, this seems like a change in behavior and will consult the release notes.

2

There is a hidden scrollbar outside of the script editor, if you scroll down outside of the editor and shift the page down you will see the whole code.

Something isn’t being accounted for when calculating the height of that code box. There’s also a width issue. if you make those scroll bars visible through DevTools its easier to see what’s happening.

I had to push the height to subtract around 180px to get it to sit correctly (it was 48px before):

image
image1048×231 13.1 KB

3

@Owain thanks, I see that i can scroll on the left, missed that. I can’t find dev tools?

4

I figured out you were probably referring to edge developer tools.

Any thoughts on the variable passing portion? I worked in v3.9.x but in 4.x when I create a job from a script it doesn’t come across and just the string, but adds some xml?

5

This is a bug and should be fixed. I opened and issue here: Pipeline data is jobs is returned as CliXml · Issue #2500 · ironmansoftware/issues · GitHub

6

You the man, thanks.

7

Can you provide an example? I’m doing this and it seems to work.

S1.ps1

Invoke-PSUScript -Name 'S2.ps1' -Value 'Test'

S2.ps1

param($Value)

$Value

image
image716×337 7.78 KB

8

Here is how I pass it to a schedule:
S1.ps1

param (
	$ctuser
)

New-PSUSchedule -Script "UserManagement\NewEmployeeEmail.ps1" -OneTime $emailDate -useraccount $AD_SamAccountName -ctuser $ctuser -Name "New User Email for $AD_SamAccountName at $AD_Office" -Environment 'Windows PowerShell 5.1'

S2.ps1

param (
    $useraccount,
    $ctuser
)

the $AD_SamAccountName and $AD_Office are set in S1.ps1 during runtime.

Once they go to the job they are as the clixml

1 Like
9

I was trying to see how this schedule appears in the schedules.ps1 file, but it is not there? Do run once schedules save elsewhere? I see them in the schedule but when I modify them, it does not save.