WAD Reports Changeable in Prod

[Former Member]

Hello All,

I wanted to know if queries and WAD can remain changeable in production environment  ?. I have worked in both environments where the reports are less frequently changed and hence they are transported to production and in environment where the reports are frequently changed in production to enable users to have flexibility of reporting and to accommodate immediate changes.

However , we are right now in a position where reports are transported to production , where as Web application designers are created in Production directly to enable quick change .Now the client is requesting to transport WAD too .

Can anybody help me out, in what is the best practice to manage WAD's  in frequently changed environment.

Pros and Con of keep WAD reports editable in production.

Regards,

Rakesh.

[former_member182470 · Accepted solution]

Generally we can allow changeability for web templates in Prod. If you have developed i-views based on web templates, then we have to be careful that the Web template technical name doesn't get disturbed. Because, we may land up in editing i-views again. This is one concern.

We should not give this change access to all users, only to important users.

If your client is insisting to transport Wad as well, then you have to create all your web templates by looking up Prod or do a reverse transport from Prod to Dev, This is a sensitive task as transport path has to be changed in SCC1 and SCC4(client has to be opened in Prod).

[Former Member]

Pros -

- Flexibility

Cons

- No version management

- Need to import every TR that contains this WAD in overwrite mode, cos the original object is changed

- Need to maintain WAD templates that are changed in production environment. This is difficult as you cannot have control over changed objects. Headache.

WAD customizations are precise and a small change in the adjusting width/height/including web items have its toll in the web output which affects everyone who uses the template.

As you can see, cons weigh in more than pros and hence it's not advisable to have object changability of WAD templates.

One more point: Since most of the WAD contains queries in the backend and WAD is just customization of report, why would anyone want to change WAD, instead of queries directly? Cos, change in reports will be reflected in your template anyway, unless the query itself is removed.

Modify your WAD template in dev, test it, check for object alignment and if everything is fine, transport it to production. Simple.

Br, H