<!DOCTYPE HTML><html>
<head>
<meta name="Generator" content="Amazon WorkMail v3.0-4275">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>RE: ScriptedAttribute Definition results in Error: "Invalid content was found starting with element 'InputDataConnector'"</title>
</head>
<body>
<!-- begin sanitized html --><div class="bodyclass"><p style="font-family:Arial,Tahoma,Helvetica,sans-serif; font-size:small; margin:0px"><span style="background-color:#ffffff; color:#222222; font-family:arial,sans-serif; font-size:small; font-style:normal; font-variant-caps:normal; font-variant-ligatures:normal; font-weight:400; text-align:start; text-decoration-color:initial; text-decoration-style:initial; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px">> </span>You should "fix" that by building your new IDP with a supported release:</p><p style="font-family:Arial,Tahoma,Helvetica,sans-serif; font-size:small; margin:0px"> </p><p style="font-family:Arial,Tahoma,Helvetica,sans-serif; font-size:small; margin:0px"><span style="background-color:#ffffff; color:#222222; font-family:arial,sans-serif; font-size:small; font-style:normal; font-variant-caps:normal; font-variant-ligatures:normal; font-weight:400; text-align:start; text-decoration-color:initial; text-decoration-style:initial; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px">Under normal circumstances that would have been my answer, but the deployment is a small shop using a couple of different extensions. I expect it to all work fine given API stability, but I anticipated they just want to get a version they're comfortable with deployed now. Introducing a new minor version now could set roll-out back if for no reason beyond management apprehension, something that prevented me from implementing a vast number of harmless improvements when I worked for certain universities. That would be enhanced with lots of new deprecation WARNs in the logs.</span></p><p style="font-family:Arial,Tahoma,Helvetica,sans-serif; font-size:small; margin:0px"> </p><p style="font-family:Arial,Tahoma,Helvetica,sans-serif; font-size:small; margin:0px"><span style="background-color:#ffffff; color:#222222; font-family:arial,sans-serif; font-size:small; font-style:normal; font-variant-caps:normal; font-variant-ligatures:normal; font-weight:400; text-align:start; text-decoration-color:initial; text-decoration-style:initial; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px">Given 3.4.0 was just released a week ago, I think it's reasonable for them to stick to just getting the 3.3.3 roll-out done as already planned, then update to 3.4 on a test machine and later production, and finally migrate configuration files, all as a managed process.</span></p><p style="font-family:Arial,Tahoma,Helvetica,sans-serif; font-size:small; margin:0px"> </p><p style="font-family:Arial,Tahoma,Helvetica,sans-serif; font-size:small; margin:0px"><span style="background-color:#ffffff; color:#222222; font-family:arial,sans-serif; font-size:small; font-style:normal; font-variant-caps:normal; font-variant-ligatures:normal; font-weight:400; text-align:start; text-decoration-color:initial; text-decoration-style:initial; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px">I would love to have worked in a world where decisions were made on a purely technical basis and I had a lot of resources at my disposal, but I never got to.</span></p></div><!-- end sanitized html -->
</body>
</html>