How to reverse engineer an application feature

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

How to reverse engineer an application feature

Varun Bhansaly
Hi Everybody,

Figured out this good way of reverse engineering/ dissecting application
specific features, thought it would be good to share.

Suppose for a particular feature there is a need to figure out all what all
entities are affected.

We can simply do the "action" on the application's UI, thereafter use "Web
Tools > Import / Export > XML Data Export" to export all entities which
were updated after a particular time by specifying a value in "Records
Updated Since" field: its value could be "action time" + 10 seconds.

Some of the exported entities like JobSandbox, RuntimeData, ServerHit etc.
may be ignored.

For more accurate results, this should be tried on systems which no one is
else is simultaneously accessing.

--
Regards,
Varun Bhansaly
Reply | Threaded
Open this post in threaded view
|

Re: How to reverse engineer an application feature

Adrian Crum-3
You can also use the Artifact Info section of the Web Tools application.

-Adrian

On 6/7/2012 3:32 PM, varun bhansaly wrote:

> Hi Everybody,
>
> Figured out this good way of reverse engineering/ dissecting application
> specific features, thought it would be good to share.
>
> Suppose for a particular feature there is a need to figure out all what all
> entities are affected.
>
> We can simply do the "action" on the application's UI, thereafter use "Web
> Tools>  Import / Export>  XML Data Export" to export all entities which
> were updated after a particular time by specifying a value in "Records
> Updated Since" field: its value could be "action time" + 10 seconds.
>
> Some of the exported entities like JobSandbox, RuntimeData, ServerHit etc.
> may be ignored.
>
> For more accurate results, this should be tried on systems which no one is
> else is simultaneously accessing.
>