I'm new in RPA and also in BluePrism. I've been developing some objects in order to use it in other machine. The problem is that my computer has version 6.6 and the other one a lower version (6.4). I've tried to export obejct (in XML format) and as a release. But I have the same result... When I import it in the other machine, all the nodes are together in the same position (giving me extra errors). Is there a way to export an object that can be readble for older versions of bp?
Error
This exact phenomenon is well documented in this Blue Prism Community post. Your issue is likely that Blue Prism changed the way that XML is generated by the client between v6.3 and v6.6, thus leading to the "stacked" appearance of your object/process stages. The user in the linked thread implied that un-stacking the stages seems to do the trick here.
More broadly: exports and releases are somewhat backward-compatible; that is, they should work, but aren't guaranteed between releases that change the XML spec of exported processes/objects/releases.
Related
The Microsoft Edge F12 tool and the Microsoft Edge Dev Tool Preview app crash on opening. This problem does not occur on same website using new Microsoft Edge Chromium version.
I am writing this question with the intent on self answering it, after 7 lost hours of debugging
I am developing an Excel Add-in using the new Microsoft Edge WebView for office-addins, which just rolled out, and replaces IE11 as the embedded IFrame in Excel with Edge (see https://developer.microsoft.com/en-us/office/blogs/microsoft-edge-webview-for-office-add-ins/). After this last month roll out, the problem presented.
The crash is predictable, occurs after 5 seconds after activating the tool. It occurs when using F12 tools in Edge browser, and when using the standalone Dev Tools Preview to remote connect to the Edge browser running in MS Excel.
(I won't put app event logs because I have already solved it)
This is a Microsoft bug, not a coding bug.
It always occurs when using Typescript and defining a multidimensional array with only one element, and only in an async function
async myFunc(){
let x:number[][] = [[9]]; //Edge F12 tool will crash simply by having this line
}
The problem does not occur in non async functions, and does not occur if the variable is defined as a class member. It does not occur if more than one element is defined. Workaround is to define the variable as private class member
public x:number[][] = [[9]]; //ok as member variable
let x:number[][] = [[9,2]]; //ok - even in async function
For those reading this who rightly ask "why would you want to define a multidimensional array with only 1 element". It is because MS Excel is a 2D array, and to set the value of cells the Excel API expects two dimensional arrays Excel.Range.values[][] =any[][]. So if you want to set the value of only one cell, you must supply a multidimensional array with only one value.
NB. I have not raised the bug with Microsoft as they are no longer supporting the Microsoft Edge Dev Tools preview, instead focusing on rolling out the Edge Chromium version, thus deprecating these tools. The problem does not occur in the Edge Chromium developer release, but I have no idea when Edge Chromium will be rolled out as the embedded browser in Excel (we only just left IE11 behind last month)
#JimbobTheSailor
Thank you for taking the time to report the issue and also coming back to provide the possible cause of the issue.
I know you have already spent a bunch of time on this issue, but I was hoping you could provide an example code file, or even npm package, that will cause the issue? I went and added your code and attempted to reproduce the issue, but I could not. GitHub Repo! By providing the entire package, or example, I can also see the different versions of TypeScript and other dependencies. You could also just list them here as well.🙃
If possible, and don't mind grabbing it, could you provide the version of Windows you are using? START | RUN | WINVER . Also, the version of the DevTools Preview? Example:
C:\Program Files\WindowsApps\Microsoft.MicrosoftEdgeDevToolsPreview_18.924.1.0_x64__8wekyb3d8bbwe
To run my sample all you have to do is:
npm install
npm run build:dev
npm start
...or the yarn equivalent.
This will build, sideload the app, and boot Excel. 🙃
I used text node as child od node to implement align support.
It's possible to do text clipping ? I text is bigger and parent node element.
And also I need to implement word wrapping.
I heard about new 2.0 - It seems this release has implemented som of this. Someone know something about date of 2.0. release ?
regarding v2, you may already download current version on the WIP branch on GitHub.
It's still not finished (we add new samples and unexpected features and options, so we we have lost some time), but it's already stable and used on some customers projects. Time-to-time we add new things inside :)
Regarding your request, relationship between a parent node and its children is only related to transformation. That means that only transformations (scale, rotation, translation) applied to a parent will be applied to the child. Nothing regarding the size. So you cannot use it to directly align your nodes.
Anyway, you may easily develop it: you know the size of your text and your parent (using getWidth() and getHeight() methods) and their positions so you can translate the text node to be aligned with another node.
To use the word wrapping, you may use the myTextNode.setWrapMode(CGSGWrapMode.WORD, true) call.
There is also CGSGWrapMode.LETTER (default) and CGSGWrapMode.SENTENCE.
Hope this help.
I am working through the pluralsight videos on MonoTouch. At one point, the trainer right clicks on the name of a derived class, and in the 'refactor' menu there is a function to override/implement members of that class. When I click however (latest version), I see only 'rename.'
The person in this link had the same issue some time ago and has included screenshots - but noone replied to them in the MonoTouch discussion group:
http://monotouch.2284126.n4.nabble.com/Right-Click-Class-name-gt-Refactor-gt-Override-Implement-members-tt4655504.html#none
Has anyone experienced (and resolved!) this?
Some of the refactoring features were reorganized or removed (for now) in the rewrite of the code code completion engine that took place for MD 3.0.
You can still access this particular feature two ways:
1) After typing the "override" keyword, MD offers the members you can override/implement. Selecting one will cause it to be stubbed out.
2) You can override many members at once using the "Edit->Show Code Generation Window" command in the class body. This command doesn't have a keybinding on Mac by default, but you can assign one in Preferences.
MonoDevelop 3.0 (and later) removed some features (including a few about refactoring) since they were not as stable, fully functional (complete) or buggy.
The same features (or similar ones) are likely to come back in future releases.
EDIT: might be fixed in latest Xcode 4.0.2 (just released) - I'm downloading this out now, and will re-edit once I've tested it.
Create two entities (call them "Manager" and "Employee", to stick with Apple's docs).
Create a relationship, "worksFor" from Manager (1) to Employee (many), and mark it as "not optional". (you'll probably need to create 2 relationships, mark 1 as inverse of other)
Hook up an interface using IB, according to Apple's original docs (NB: these don't work any more, but here's an almost exact recreation of the basic setup in Xcode4: http://rgprojection.blogspot.com/2011/04/xcode-4-and-core-data-macos-x.html) and use Bindings (as described in the linked post) to create/add/delete the objects.
Now try to save. ERROR: "worksFor is a required property".
In previous versions of Xcode, this worked as expected: you'd told Xcode that there was a bidirectional relationship, you told it that it was required, and so when it added the "Employee" to the "Manager", it automatically hooked-up the inverse.
Has anyone else worked out how to make Xcode4 do what it's supposed to? Is it an Xcode4 bug? I know that some of the CoreData support in Xcode4 has been deleted, with no replacement (yet), so I'm wondering if this has been deleted too?!
EDIT: here's another project, one I made from scratch, same problem. Although (xcode4 bug, definitely!) this time I created the Relationship in the "grid" editor view rather than the "tree graphical" view... and the generated source code for objects was different (should not be the case, obviously)
second project screenshot
EDIT2: StackOverflow was showing the screenshot above, but has now removed it, you'll have to click on the link. Sorry.
I haven't seen the problem you describe and I've created several data models under Xcode4. It appears to work just like it did in previous versions in that regard. I think you've got something else going on.
Xcode 4.0.2 seems to have fixed the problem - everything works as expected now, with no changes to code :)
I have an XSD that's going through a transition from one set of elements to another. During the transition, there'll be code expecting the new elements and code expecting the old elements. Therefore I need to keep the old elements in the XSD; I'm documenting them as deprecated (using free text in an xs:documentation element).
Is there a way of marking an element as deprecated such that a tool like xmllint will automatically warn if someone uses a deprecated element?
Create a new schema, with a new namespace. Call this "version 2". If you choose to support version 1 XSD and version 2 XSD in your application that's fine, but keep them seperate and don't try to layer the two on top of each other - especially if you're going try to stop people from using the version 1.
This is worth looking at as it describes some of what you're dealing with:
archive of http://www.pluralsight.com/community/blogs/tewald/archive/2006/04/19/22111.aspx
I realise, however, that doesn't really address your question. With regard to "is there a way to do this?" the answer is "no - not in a universally supported manner". I've seen people add their own doc annotations to give hints, but this isn't going to be universally understood by tooling.
Your best bet in the long run is to create come up with a versioning story for your schema(s) and keep version 2 seperate from version 1.