When using the Copy Data Element to New Location component, use the “Deep Copy” option if you mean to retain the original variable for comparison purposes and you intend to edit the values of the copied (new) variable. See the demo for a better illustration, but here’s a scenario to hopefully help describe it:
Bugs
Workflow 7.6 – Adjustments and Considerations
{{Update 7/6/2015:
The TextBox component is now a nested input element. any javascript or CSS reference to a TextBox component will now need to be adjusted to fit the new HTML layout.
.textbox {
outline: none;
}.textbox > input {
outline: none;
}
var txtbx = document.getElementById(‘textbox’);var txtbx = document.getElementById(‘textbox’).firstElementChild;
}}
After working with 7.6 for a few days, I’ve found a few bugs, as well as some differences in how the javascript is rendered in the new version. I’ll also mention that the 7.6 virtual windows are completely different than the old infragistics stuff in 7.5; you’ll actually notice if you go looking for it, that the infragistics folder isn’t even there anymore.
“Object reference not set…” – Salvaging a Busted Project
It’s been a while since the last post – I’ve been busy with an Endpoint Summit (I’ll post the likely embarrassing video after Symantec does) and several customers, and my free time has been consumed with family and Dark Souls II. So it’s past time that I post something.
During a working session with a customer two weeks back, I ran into something I haven’t seen in a while. After making some major changes with data types and mapping in the project, I attempted to spool the debugger, and got this:
Now, once upon a time, this error meant to me that “oh crap, there goes an hour’s worth of unsaved progress”, because this problem prevents saving the project as well. While I don’t have a sincere diagnosis for the problem, I certainly figured out the hammer as a solution.
atmaworkflow 